Align shared project conventions and release v0.1.4. - #12
Merged
Merged
Conversation
samuel-williams-shopify
force-pushed
the
codex/consistency-patch-20261006
branch
from
October 5, 2026 12:16
ad56863 to
3375656
Compare
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.
Release
socketryv0.1.4 with the current Socketry project conventions.Adopt
socketry-project >=0.3.7in the private Bake package and resolve the lockfile to 0.3.7 with one shared Bake registry. Add the stabletest-resultgate, refresh agent context guidance and dependency examples, and let the shared version hook normalize the standard Markdown and public context files. Repository rulesets now require publishing checks and the aggregate test and coverage result.The existing sanitizer jobs remain diagnostic and are excluded from the required aggregate while their failures are investigated separately. Regular tests, coverage, io_uring, and FreeBSD remain required.