Skip to content

Refresh examples against published 2.8 package versions - #57

Merged
bluejeans117 merged 1 commit into
mainfrom
chore/refresh-2.8-example-locks
Sep 5, 2026
Merged

Refresh examples against published 2.8 package versions#57
bluejeans117 merged 1 commit into
mainfrom
chore/refresh-2.8-example-locks

Conversation

@bluejeans117

Copy link
Copy Markdown
Collaborator

Summary

  • refresh the standalone Express, Fastify, and Hono package-lock.json files to resolve @prauga/flexdoc-backend@2.8.0 now that the coordinated JavaScript release is published
  • refresh examples/rust-axum/Cargo.lock to the published prauga-flexdoc-axum@0.4.0 crate
  • replace the pre-release Go v0.4.0 checksum placeholders in all committed Go example go.sum files with the public Go proxy-authoritative checksum after the tag became available

No example manifests, source code, or product versions change in this PR; it only closes the post-publication lock/checksum gap.

Validation

  • node scripts/check-example-versions.mjs
  • node scripts/verify-go-example-sum.mjs
  • locked npm ci for Express, Fastify, and Hono standalone examples
  • cargo check --locked --manifest-path examples/rust-axum/Cargo.toml
  • go mod download && go test ./... for net/http, Gin, Chi, Echo, and Fiber examples
  • focused diff guard confirmed only the nine expected lock/checksum files changed

Refresh the standalone Express, Fastify, and Hono npm locks to @prauga/flexdoc-backend 2.8.0, the Rust Axum example lock to prauga-flexdoc-axum 0.4.0, and all Go example sums to the public proxy checksum for adapters/go v0.4.0 after publication. Verify locked installs, example version guards, and representative example builds.
@bluejeans117
bluejeans117 merged commit 67577b8 into main Sep 5, 2026
3 checks passed
@bluejeans117
bluejeans117 deleted the chore/refresh-2.8-example-locks branch September 5, 2026 15:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant