Repository navigation
Bump framework release to 0.1.1177 - #3174
Merged
Merged
Conversation
Constraint: 0.1.1177 is unused on npm and has no matching git tag; this branch now sits directly on main after #3173 merged. Rejected: publishing from the redaction fix PR directly | keeps the privacy fix and release bump reviewable as separate steps. Confidence: high Scope-risk: narrow Directive: Keep this PR draft until the release handoff is ready; do not publish without the normal release gate. Tested: npm availability checks for veryfront and @veryfront/ext-observability-sentry; git tag availability check; deno task generate:manifests:check; deno task fmt:check; deno test --no-check --allow-read src/utils/version.test.ts; deno task typecheck Not-tested: full deno task verify; publish workflow; production deployment; pre-commit verify:quick previously failed on a pre-existing release-assets docs/API-reference gap unrelated to this bump
kwakayama
force-pushed
the
agent/code-sentry-redaction-1177
branch
from
July 29, 2026 22:03
4db9791 to
d3e5ac9
Compare
Contributor
Author
|
Review complete — 96/100, APPROVE. Architecture: CLEAR.
No CRITICAL/HIGH/MEDIUM/LOW findings remain. |
kwakayama
marked this pull request as ready for review
July 29, 2026 22:06
kwakayama
enabled auto-merge
July 29, 2026 22:06
kojiwakayama
approved these changes
Jul 29, 2026
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
2 participants
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.
Summary
Bumps the framework release metadata from 0.1.1176 to 0.1.1177 for the structured-log redaction fix that merged in #3173.
This PR now sits directly on
mainat #3173's merge commit and remains draft until the release handoff is ready.Scope
deno.jsonversion ->0.1.1177src/utils/version-constant.tsVERSION ->0.1.1177Base / History
15951b72c0eb6b8facf0096604fac44f016cf78forigin/mainValidation
npm view veryfront@0.1.1177 version-> 404 / unusednpm view @veryfront/ext-observability-sentry@0.1.1177 version-> 404 / unusedgit ls-remote --tags origin v0.1.1177-> no tagdeno task generate:manifests:check-> passeddeno task fmt:check-> passeddeno test --no-check --allow-read src/utils/version.test.ts-> passed, including VERSION / deno.json syncdeno task typecheck-> passedNotes
Pre-commit
verify:quickwas attempted before the rebase and failed on an existing docs/API-reference gap for./release-assets, not on this version bump. This PR stays scoped to release metadata only.