Repository navigation
Prepare the first release, 0.1.0 - #144
Merged
Merged
Conversation
Provide a versioned release boundary for Git consumers and derive GitHub release notes from the initial capabilities. Reject inconsistent tag, package and changelog versions before publishing a release. Part of #143
Send the published release link after creation succeeds, and keep notification retries separate so a Slack outage does not require recreating a release. Document the webhook secret setup. Part of #143
Follow the existing release integration pattern: the workflow creates GitHub Releases and Slack subscribes to their publication. Keep the channel subscription check in the documented release procedure. Part of #143
Keep the release checklist in its issue so the library README stays focused on the crate's capabilities and usage. Part of #143
Match aimer's ownership notice for the first release. Part of #143
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.
Prepare deploy-core's first release, 0.1.0, following review-web's bare version tags and changelog-driven GitHub Releases. The package version is already 0.1.0.
The changelog now describes the initial library capabilities in a dated 0.1.0 section, replacing the accumulated pre-release migration history. Add a tag-triggered release workflow that checks the tag against Cargo.toml and extracts exactly one nonempty matching changelog section before creating a GitHub Release. Markdown is preserved and changelog link definitions are excluded. The release issue records the human merge, annotated-tag and tag-push steps; this PR publishes neither a tag nor a release, binary assets or a crates.io package.
Slack announcements use the GitHub integration for Slack subscribed to published releases, while release.yml creates the GitHub Release as in review-web. The release issue records
/github subscribe aicers/deploy-core releases; confirming the announcement channel subscription is a release checklist item. No custom Slack webhook or Actions secret is required. The Slack subscription itself has not been verified from this environment.README uses the same copyright notice as aimer:
Copyright 2026 ClumL Inc.Part of #143
Validation
After merge and successful main CI, create an annotated
0.1.0tag on the merged commit and push that tag. Confirm the Release workflow, notes and Slack announcement before completing the release issue.