Repository navigation
Simplify Publish to tag releases the way Chronicle does - #2
Merged
Merged
Conversation
The workflow called a reusable kit-release.yml that also tried to push AI corpus updates back to main using a KIT_RELEASE_TOKEN secret that was never configured in this repository, so every Publish run failed before any job started - merging did not even cut a release. Publish only ever needed to tag and create the GitHub release, exactly like Chronicle's publish.yml does. Call cratis/release-action directly with the default token and drop the corpus-sync job; the AI corpus is kept current with cratis ai update as its own deliberate step.
The no-release job ran git diff against the base and head SHAs without ever checking the repository out, so it had no git history to diff against and failed outright the first time a PR actually carried the no-release label.
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
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.
Changed
Publishnow callscratis/release-actiondirectly with the default token instead of a reusable workflow that also tried to push AI corpus updates back tomainusing aKIT_RELEASE_TOKENsecret that was never configured. EveryPublishrun failed before any job started, so merges never cut a release. The AI corpus is kept current withcratis ai updateas its own step, not tied to publishing.