Repository navigation
ci: publish archunit automatically from main - #95
Merged
Merged
Conversation
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.
Main-branch changes currently cannot publish
archunitwithout a manual release and separate trusted-publisher setup. This change runs the full CI matrix before publishing to crates.io with the encrypted repository secret, automatically advances patch versions, and verifies an exact-version registry consumer before creating a tag and GitHub release.Release metadata is committed back to main without force pushing. Retries recover the same metadata commit and compare the registry archive's source SHA to avoid publishing an accepted version twice. Product changes still use PRs; automated version metadata is the documented exception.
Validation: actionlint passed; 9 Python release tests passed, including a real Git partial-release recovery scenario; all 5 Rust release-workflow tests passed; formatting and whitespace checks passed. The PR CI provides the full cross-platform, MSRV, Clippy, documentation, and packaging gates.
Refs #44.