chore(timeglyph): release v0.9.8 - #30
Merged
Merged
Conversation
h4x0r
force-pushed
the
release-plz-2026-08-20T09-47-54Z
branch
2 times, most recently
from
August 20, 2026 22:20
7a12b67 to
ea88a4e
Compare
h4x0r
force-pushed
the
release-plz-2026-08-20T09-47-54Z
branch
from
August 20, 2026 23:21
ea88a4e to
9e0c24e
Compare
release-plz manages the root workspace lock, but `lens/` is a separate (Windows-only) workspace with its own Cargo.lock, so it was left pinning `timeglyph 0.9.7` (plus other deps behind latest) after the version bump — the `freshness` job's `cargo update --locked --manifest-path lens/Cargo.toml` caught it truthfully. Bring the lens lock fully current (timeglyph -> 0.9.8 via the path dep + latest compatible deps); `cargo update --locked` now locks 0 packages. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Refreshing the locks (freshness) bumped six third-party deps to new patch/minor versions, which their exemptions no longer matched. Version churn of already-covered crates is bookkeeping, not a new supply-chain decision (ADR-0018): bump the five existing exemptions to the new versions (crc32fast 1.5.1, icu_provider 2.3.1, log 0.4.34, uuid 1.25.0, zerovec-derive 0.11.6) and trust syn via dtolnay (mozilla/bytecode-alliance already trust the publisher). `cargo vet` succeeds. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
h4x0r
added a commit
that referenced
this pull request
Sep 15, 2026
Stop the freshness gate from breaking on every timeglyph release. release-plz regenerates only the root workspace lock; `lens/` is a separate workspace (excluded because it is Windows-only) with its own committed Cargo.lock, so after each version bump it still pins the previous `timeglyph` path-dep version and the freshness job's `cargo update --locked --manifest-path lens/Cargo.toml` fails (as it did on 0.9.8, #30). Add a release-plz-pr post-step that refreshes lens/Cargo.lock on the same release PR branch whenever a release PR exists. lens is not published, so this touches no cargo-vet attestations. The step is guarded (exits cleanly if there is no release PR branch) and only commits when the lock actually changes. wasm/bindings-python/fuzz keep no committed lock, so freshness does not gate them and they need no handling. Co-authored-by: Claude Opus 5 <noreply@anthropic.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.
🤖 New release
timeglyph: 0.9.7 -> 0.9.8 (✓ API compatible changes)Changelog
This PR was generated with release-plz.