Skip to content

chore: re-enable the semver check and pin the readme example #88

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
polaz merged 2 commits into from
Sep 20, 2026
Merged

chore: re-enable the semver check and pin the readme example #88

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ba19055
chore: re-enable the release-plz semver check
polaz Sep 20, 2026
b1c40f0
docs: pin the readme example to the current major
polaz Sep 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -397,7 +397,7 @@ that injects its own verifier is not in that argument at all: it takes

```toml
[dependencies]
structured-proxy = { version = "3", default-features = false }
structured-proxy = { version = "4", default-features = false }
# What the verifier above is written with: the trait is `#[async_trait]`, and
# claims cross it as `serde_json::Value`. Neither is re-exported.
async-trait = "0.1"
Expand Down
5 changes: 0 additions & 5 deletions release-plz.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,5 @@
[[package]]
name = "structured-proxy"
# cargo-semver-checks builds the baseline from the registry, and every version
# published so far rejects the feature set it uses (both JWT backends at once).
# The published artefacts cannot be changed, so the check stays off until a
# release carrying that fix becomes the baseline; see issue #84.
semver_check = false
# Preserve the existing tag scheme (v1.0.0, v1.0.1, ...) instead of the
# release-plz default of "{package}-v{version}", so tag history stays continuous.
git_tag_name = "v{{ version }}"
Loading