chore(deps-dev): bump @types/node from 25.9.2 to 26.0.0 in /bpk-ts#133
Closed
dependabot[bot] wants to merge 1 commit into
Closed
chore(deps-dev): bump @types/node from 25.9.2 to 26.0.0 in /bpk-ts#133dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 25.9.2 to 26.0.0. - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) --- updated-dependencies: - dependency-name: "@types/node" dependency-version: 26.0.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
heyoub
added a commit
that referenced
this pull request
Jul 2, 2026
…n ctor (#133) Store::open refuses linked EventKind collisions (FailFast), but a RELEASE binary that registers colliding payloads and never opens a Store got no check (the derive's collision check is cfg(test)-only). The derive's inventory registration is already unconditional, so no derive change is needed — only a scan-invocation path. Two paths (owner: A4 + optional ctor): - verify_registry() — a documented public alias over validate_event_payload_registry() (re-exported at event::payload / event / prelude). Call it once at startup if your binary registers EventPayload types but may not open a Store. Portable, no dep. - `startup-registry-check` (NON-default) cargo feature -> optional `ctor` dep + one central #[ctor] fn that scans at load and, on a collision, writes a diagnostic via stderr().write_all (not eprintln — print_stderr is banned) then process::abort(). Native automatic life-before-main; the default build pulls NO ctor (cargo tree confirmed). Red fixtures (crates/core/fixtures/registry-startup-{collision,ctor}/ + driver event_payload_registry_startup.rs, --release subprocess, mirroring the downstream fixture precedent): collide_verify -> exit 1 + "duplicate kind assignment" stderr; collide_ctor (--features) -> SIGABRT before main; clean_verify (control) -> exit 0. Baseline +3 (verify_registry at the 3 paths); syncbat/netbat byte-identical. Both builds green: fmt, clippy x2, build x2 (no ctor by default), structural ok. ctor clears cargo-deny (MIT/Apache). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NHio8XCrH89gdEcycCumr6
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 @types/node from 25.9.2 to 26.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)