Repository navigation
chore(*): prepare beta packages - #49
Merged
Merged
Conversation
omermorad
changed the title
omermorad
marked this pull request as ready for review
October 31, 2026 04:57
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.
Prepare the beta versions generated by the Prepare Release workflow at commit 86ba74f:
@contractual/cli,@contractual/differs.json-schema,@contractual/differs.openapi, and@contractual/governance:0.1.0-beta.1to0.1.0-beta.2, with generated changelogs.@contractual/changesets,@contractual/differs.core, and@contractual/typesremain at0.1.0-beta.1because Lerna detected no package changes.The build, 14 unit tests, and 361 end-to-end tests passed in run 41170270407. The run pushed this branch, then failed to create its PR because organization policy prohibits Actions from creating or approving pull requests. This PR recovers the already-prepared branch without regenerating versions.
Release review required: the unchanged beta.1 packages still have tags at the earlier approved commit. The current publish workflow requires every existing package tag to match the new approved release commit. Resolve that version/tag plan before publishing; do not move existing tags implicitly.
This PR does not create tags or publish packages. Publication requires separate explicit approval from Omer.