Skip to content

Promote staging -> main (Release runtime metadata) #54

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
0xPlayerOne merged 1 commit into from
Jul 28, 2026
Merged

Promote staging -> main (Release runtime metadata) #54

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,11 @@ CodeQL is also independently reusable through the same contract. It retains
GitHub's native security-event permissions and language-specific analysis while
keeping CodeQL separate from CI and dependency security checks.

Release automation follows the same model: the consumer keeps a short
main-branch wrapper while the shared runtime handles Release Please, GitHub
release metadata, optional npm publication, provenance, and token/trusted
publishing fallback.

Initialization defaults to AGPL for new repositories. Synchronization defaults
to `--license preserve`, so an existing repository's license is never replaced
unless you explicitly select a license or provide `--license-file`.
Expand Down