Repository navigation
chore(deps): bump wast from 262.0.0 to 263.0.0 - #1630
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [wast](https://github.com/bytecodealliance/wasm-tools) from 262.0.0 to 263.0.0. - [Release notes](https://github.com/bytecodealliance/wasm-tools/releases) - [Commits](https://github.com/bytecodealliance/wasm-tools/commits) --- updated-dependencies: - dependency-name: wast dependency-version: 263.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
Contributor
|
temper did not enable auto-merge: breaking update wast 262.0.0 -> 263.0.0 needs a human review. |
github-actions
Bot
added
the
major-bump-hold
|
🔒 HELD — not auto-mergeable (class: Auto-merge has been actively disabled and asserted off by the hold gate (#965). For a 0.x crate the MINOR component is the de-facto major (and for 0.0.x, the patch): |
avrabe
added a commit
that referenced
this pull request
Nov 5, 2026
Dependabot rejects a top-level `groups:` key ("The property '#/' contains
additional properties ["groups"]"), so every commit since #1625 carries a
failing `.github/dependabot.yml` check and no grouped update is applied.
Groups are per updates-entry and inherit that entry's ecosystem:
- github-actions entry: github-actions-all, pattern "*" (all action pins
in / as one PR). The regex "^[^@]+/" from #1627 is not a dependabot
pattern (patterns are globs), so it matched nothing.
- cargo entry: wasm-tools-family (adds "wast", which arrived as its own
PR #1630 alongside the 0.263 family bump) and wasmtime.
Supersedes the content of the earlier version of this PR, which nested all
three groups under the github-actions entry, where the cargo groups could
never match.
Refs #1625 #1627
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01YJK5LZZEkV5smCY1jKn18L
avrabe
added a commit
that referenced
this pull request
Nov 5, 2026
Dependabot rejects a top-level `groups:` key ("The property '#/' contains
additional properties ["groups"]"), so every commit since #1625 carries a
failing `.github/dependabot.yml` check and no grouped update is applied.
Groups are per updates-entry and inherit that entry's ecosystem:
- github-actions entry: github-actions-all, pattern "*" (all action pins
in / as one PR). The regex "^[^@]+/" from #1627 is not a dependabot
pattern (patterns are globs), so it matched nothing.
- cargo entry: wasm-tools-family (adds "wast", which arrived as its own
PR #1630 alongside the 0.263 family bump) and wasmtime.
Supersedes the content of the earlier version of this PR, which nested all
three groups under the github-actions entry, where the cargo groups could
never match.
Refs #1625 #1627
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01YJK5LZZEkV5smCY1jKn18L
avrabe
added a commit
that referenced
this pull request
Nov 5, 2026
…mory for gale (#1622), and the release tooling reads a patch release as its own release (#1624) * v0.89.1 PATCHVER: the release tooling reads a patch release as its own release One canonical release key (status_evidence_check.release_key / parse_release / fmt_release), imported by issue_closure_check and loop_conformance_check: vX.Y and vX.Y.0 key as (X, Y) exactly as before, a patch vX.Y.P (P >= 1) keys as (X, Y, P). release-v0.89.1/ is no longer folded into v0.89; the patch lane subject is recognised; the patch window opens at v0.89.0; --release v0.89.1 audits the patch's own close-set; the CENSUS and --from-anchor name the patch when its directory is present; the ci.yml issue-scope shape pin accepts vX.Y.Z. Every existing two-part release's gate output is byte-identical. Refs #1622 Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01YJK5LZZEkV5smCY1jKn18L * v0.89.1 PATCHVER: assemble the v0.89.1 patch — records, anchor at v0.89.0, version 0.89.1, notes Turns the PATCHVER tooling PR into the whole v0.89.1 patch release that ships #1622 (i64 load/store on a non-default memory) to gale. - artifacts/release-v0.89.1/: a comments-only _release.yaml (statistics scan: 0 digit, 0 word-number hits); RQ-89-MEMK64 (implemented, its issue #1622 in issue-scope, landed PR #1623 c874396; the memk_i64_1622 differential re-run on the 0.89.1 binary: compared 5484, ORACLE: PASS; multi_memory_406 23/23); RQ-89-PATCHVER (the tooling record this PR's subject names); RQ-89-ARCHMODEL9 (the steps-1-2 filing for v0.89.1, #1136, deferred); RQ-89-ACTIONPIN (proposed/partial: attributes the delivery-typed `fix(dependabot)` #1627 subject R10 requires, with #1625/#1626; its refuting grep finds 2 release tags #1626 did not pin). - Anchor moved to v0.89.0 in status_evidence_check.py and its claims.yaml mirror: delivery 134, programme 687, read off the gate's own anchor line; 133/135 and 686/688 each red, the old 662 red at v0.89.0. - recurring_na_filing_check keys releases with status_evidence_check's release key and expected_cut, so the cut is v0.89.1 (main's script on this tree refuses as "ambiguous: v0.90 vs v0.89"). - test_issue_closure_check's --from-anchor case derives the successor from the patch directory's presence (it hard-coded minor+1, red here). - Version 0.89.0 -> 0.89.1: workspace, path-dep pins, MODULE.bazel, npm, FEATURE_MATRIX, Cargo.lock (19 synth crates, nothing else). - CHANGELOG [0.89.1]; artifacts/status.json regenerated. Refs #1622 #1136 Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01YJK5LZZEkV5smCY1jKn18L * ci(dependabot): define each group under the updates entry it belongs to Dependabot rejects a top-level `groups:` key ("The property '#/' contains additional properties ["groups"]"), so every commit since #1625 carries a failing `.github/dependabot.yml` check and no grouped update is applied. Groups are per updates-entry and inherit that entry's ecosystem: - github-actions entry: github-actions-all, pattern "*" (all action pins in / as one PR). The regex "^[^@]+/" from #1627 is not a dependabot pattern (patterns are globs), so it matched nothing. - cargo entry: wasm-tools-family (adds "wast", which arrived as its own PR #1630 alongside the 0.263 family bump) and wasmtime. Supersedes the content of the earlier version of this PR, which nested all three groups under the github-actions entry, where the cargo groups could never match. Refs #1625 #1627 Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01YJK5LZZEkV5smCY1jKn18L --------- Co-authored-by: Claude Opus 5.5 <[email protected]>
Contributor
Author
|
Superseded by #1649. |
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.
Bumps wast from 262.0.0 to 263.0.0.
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)