release: 0.1.0-alpha.5 — Python Verdict.allow(), linux-arm64-gnu napi target - #65
Merged
Merged
Conversation
Every other SDK exposes a no-argument trivial-permit constructor (Rust Verdict::allow, TypeScript Verdict.allow(), .NET Verdict.Allow, Go AllowVerdict); Python offered only the module-level ALLOW constant. Add the classmethod for cross-SDK naming parity and switch the README interceptor example to the sugar forms. Signed-off-by: MohammadHaroonAbuomar <40180927+MohammadHaroonAbuomar@users.noreply.github.com>
Add aarch64-unknown-linux-gnu to the napi target set with a committed npm/linux-arm64-gnu package dir (standard napi-rs layout; the loader already resolves it), build it natively on the ubuntu-24.04-arm hosted runner in the release matrix, and extend the publish-time optionalDependencies injection plus the publish loop. A never-published npm package cannot carry a trusted publisher, so its first OIDC publish fails; the publish loop now fails soft for exactly that case (warning, run continues) — bootstrap the package, configure its trusted publisher, and rerun the idempotent workflow. musl targets stay unshipped: the pipeline builds on native runners only and linux-x64-musl does not ship either; a musl pair can land together later. Signed-off-by: MohammadHaroonAbuomar <40180927+MohammadHaroonAbuomar@users.noreply.github.com>
All four SDK manifests, their lockfiles and the committed npm platform package dirs move to 0.1.0-alpha.5 (scripts/check-version-consistency passes). The CHANGELOG folds the Unreleased §12.1 spec items (#64) into the alpha.5 section alongside Python Verdict.allow() and the new linux-arm64-gnu napi target. Signed-off-by: MohammadHaroonAbuomar <40180927+MohammadHaroonAbuomar@users.noreply.github.com>
MohammadHaroonAbuomar
requested a review
from Caitie McCaffrey (CaitieM20)
as a code owner
August 7, 2026 06:02
The generated loader embeds the package version in its NAPI_RS_ENFORCE_VERSION_CHECK guards; the CI drift gate rebuilds and diffs it, so the bump must ship the regenerated file. Version strings are the only change. Signed-off-by: MohammadHaroonAbuomar <40180927+MohammadHaroonAbuomar@users.noreply.github.com>
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.
Prepares and versions the 0.1.0-alpha.5 release.
What
Verdict.allow()— no-argument trivial-permit constructor sugar, completing cross-SDK parity (RustVerdict::allow, TSVerdict.allow(), .NETVerdict.Allow, GoAllowVerdict). Test added; Python README example switched to the sugar forms.linux-arm64-gnuplatform package —aarch64-unknown-linux-gnuadded to the napi target set, committednpm/linux-arm64-gnu/package dir (standard napi-rs layout; the generated loader already resolves it), native build onubuntu-24.04-armin the release matrix, publish-timeoptionalDependenciesinjection extended. The npm publish loop now fails soft when a never-published package cannot OIDC-publish (trusted publishers cannot be configured pre-first-publish); existing packages still hard-fail.musl targets deliberately not added: the pipeline builds on native runners only and
linux-x64-musldoes not ship either; a musl pair can land together later.Verification
scripts/check-version-consistency.py— surfaces agree at 0.1.0-alpha.5actionlint(pinned v1.7.12, checksum-verified) — cleanruff format --check/ruff checkat the CI-pinned 0.15.21 — cleanpytest sdk/python/tests -p no:agent_hooks_ctk— 181 passed, 2 skippedcargo test --locked --workspace --all-features(sdk/rust) — greennpm ci && npx tsc(sdk/typescript) — greenFollow-up (release time)
First publish of
@responsibleai/agent-hooks-linux-arm64-gnuwill warn-and-skip until the package is bootstrapped on npmjs.com and its trusted publisher configured; the release workflow is idempotent and can be rerun after.