Repository navigation
release: promote develop for 0.5.0 - #58
Merged
Merged
Conversation
Publishing runs in the npm environment, which now only deploys from main, so the workflow no longer needs its own GITHUB_REF check.
* feat: contract ORM API and recover failed migration cleanup * fix: guard migration lifetimes and load project entries by file URL * ci: preserve the required package check across platform gates
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.
Purpose
Promote the reviewed ORM 0.5.0 candidate from
developtomain.Package readiness
d521612ac2d67f864a6a00fec720a57106040f2bpasses the Linux, macOS, and Windows package gates, PostgreSQL 16, 17, and 18 integration plus installed-generation checks, and CodeQL.v0.5.0tag nor@askrjs/orm@0.5.0existed in GitHub/npm.Release evidence
After merge, run the main-branch
Publish Packageworkflow. Read back its exact main SHA, verify thev0.5.0tag dereferences to that SHA, then verify npm tarball integrity and a clean public consumer install once registry indexing completes.