Align release pipeline with devkit; fix LICENSE year#1
Merged
Conversation
The MIT block was added in 0cc6e27 with year 2025, but the repo's public history begins in 2026.
GitHub runner's shellcheck flags the `cd X && Y || true` pattern. The preceding `cd "$DEVKIT_ROOT" &&` is dead code anyway — agent-prompt.sh prefers the explicit DEVKIT_ROOT env var over pwd-based discovery.
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
f0e4e11): whenmanifest.jsonis not ahead of the latest tag, the workflow now auto-bumps the patch, writes it back, commits, and pushes viasecrets.VERSION_BUMP_KEY— matching core devkit's behavior. Release notes generation also tries both## ${VERSION}and## v${VERSION}CHANGELOG headers for full parity.6356c9a): Codex MCP config now setsCLAUDE_PLUGIN_ROOTso the devkit MCP server can resolve the canonical workflow tree when spawned from a consumer repo.97f8e74): copyright year corrected from 2025 to 2026.Test plan
This PR also serves as the first live exercise of the release workflow.
versionjob auto-bumpsmanifest.jsonfrom0.0.1to0.0.2(since0.0.1equals the future latest tagv0.0.1once tagged, but pre-tag the comparison is0.0.1vs0.0.0→ manual bump path, so this run should detect a "manual" bump of0.0.1)Commit version bumpstep either pushes a bump commit or correctly no-opscreate-releasetags the version commit, builds the source tarball, uploadschecksums.txt, flips draft to publishedDeploy key +
VERSION_BUMP_KEYsecret are already configured.