Repository navigation
chore(release): prepare Testing 0.5.0 on current develop - #51
Open
smiggleworth wants to merge 2 commits into
Open
smiggleworth wants to merge 2 commits into
smiggleworth wants to merge 2 commits into
Conversation
This branch has not been deployed
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.
Changes
@askrjs/testing0.5.0 and its Server 0.5 peer range, carrying the reviewed candidate test/configuration and normal packed-consumer installation changes.This implementation PR targets
develop. The existingdevelop→mainpromotion PR #50 stays separate and open.Local qualification
Qualified with Node 24.21.0 and npm 12.0.1 against the read-only loopback candidate registry containing the exact qualified Core, Auth, Schema, and Server 0.5.0 archives. Verified the registry identity and the supplied Server archive SHA512 before installation. No workspace links or peer-dependency bypasses were used.
npm ci: passed.npm run check: passed formatting, lint, typecheck, 67 tests with configured coverage thresholds, build, declaration checks, publint, packed-package shape, TypeScript 6/7 consumer contracts, and runtime consumer checks.npm packfrom the committed head: passed; nine package files.Exact candidate commit:
ac32742f7ae23d0f2c76d3f32056cf16e0b1d633.Archive SHA512:
191de42b37e6704c7294afa359f21cf1f0072ba92ab540dfccfeb4b8d33ce874a4d0f73e14567e6bf65450b866a8876ffdc65d236f5751e8c451048c63c3a3aa.Archive integrity:
sha512-GR3kKzfmcExylK+jWfIc8fAHK6kqtUDfzP60uNM86HSk0Pc+FFZ+a/ZUULhmqIdv/cZdI29XUejEUQSMY8Ojqg==.Local evidence:
/tmp/askr-testing-current-050-20261013/qualification.jsonand its referenced logs; archive:/tmp/askr-testing-current-050-20261013/artifacts/askrjs-testing-0.5.0.tgz.Hosted and release boundary
Hosted readback at the exact candidate head: CI run 38328337601 failed during
npm cion Linux, macOS, and Windows with npm E404 fetching the unpublished public@askrjs/server@0.5.0archive; package gates were skipped. Both CodeQL analyses passed. Local candidate qualification does not claim hosted CI is green. Exact candidate graph reconstruction, develop integration, final release acceptance, and main promotion remain separate. This PR does not publish or tag packages.