Skip to content

chore: release - #200

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main
Closed

chore: release#200
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 14, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

plugin-rest-cache: 5.1.0

5.1.0 (2026-08-14)

Features

  • add a cache statistics endpoint for the admin dashboard (594ba4a)
  • add a cache statistics endpoint for the admin dashboard (56aeae4)
  • add an opt-in content API purge endpoint (59d1153)
  • add an opt-in content API purge endpoint (ed4f778)
  • admin: rewrite the admin panel in TypeScript and add a dashboard (#181) (4db948f)
  • document service invalidation, custom route fix, and content type/API name mismatch fix (a6a289a)
  • emit Cache-Control headers on cached responses (#201) (ee75158)
  • invalidate cache from the document service (2a6903a)
  • support caching authenticated requests (23f84a4)
  • support caching authenticated requests (155af0a)

Bug Fixes

  • admin: make the panel work in a production build, and test it (#184) (5c0a229)
  • await the cache purge instead of deferring it to onCommit (9675095)
  • cache custom routes whose path ends in a repeatable param (b38d827)
  • coalesce concurrent cache misses and stop racing the purge (52b0b44)
  • coalesce concurrent cache misses and stop racing the purge (b51ee55)
  • correct 1000x cache TTL inflation and purge on all admin write routes (5dc7a20)
  • correct 1000x cache TTL inflation and purge on all admin write routes (8197205)
  • load providers reliably across Node versions and module shapes (ce7215a)
  • load providers reliably across Node versions and module shapes (c403830)
  • refuse to cache responses that cannot be safely replayed (5ccde8a)
  • refuse to cache responses that cannot be safely replayed (714f8f0)
  • resolve cache providers from the Strapi application root (#197) (691f3ff)
  • resolve default routes from the API in the uid, not the singular name (552763b)
  • restore the lodash dependency and guard against undeclared imports (566c841)

Performance

  • batch cache purges instead of one round trip per key (2574d82)
  • batch cache purges instead of one round trip per key (face64d)

Refactoring

  • drop chalk for node:util styleText, and make bad benchmarks visible (b1e9216)
  • drop chalk for node:util styleText, and make bad benchmarks visible (e71f456)
  • plugin: rewrite the server in TypeScript (#179) (586e681)

Documentation

  • give every published package a README (#196) (2f53e09)
  • sync README with the published 5.0.1 and backfill changelogs (380997c)
  • sync README with the published 5.0.1 and backfill changelogs (9878fbb)
provider-rest-cache-memory: 5.1.0

5.1.0 (2026-08-14)

Bug Fixes

  • correct 1000x cache TTL inflation and purge on all admin write routes (5dc7a20)
  • correct 1000x cache TTL inflation and purge on all admin write routes (8197205)
  • load providers reliably across Node versions and module shapes (ce7215a)
  • load providers reliably across Node versions and module shapes (c403830)

Performance

  • batch cache purges instead of one round trip per key (2574d82)
  • batch cache purges instead of one round trip per key (face64d)

Refactoring

  • providers: convert both provider packages to TypeScript (#188) (c46540f)

Documentation

  • give every published package a README (#196) (2f53e09)
  • sync README with the published 5.0.1 and backfill changelogs (380997c)
  • sync README with the published 5.0.1 and backfill changelogs (9878fbb)
provider-rest-cache-redis: 5.1.0

5.1.0 (2026-08-14)

Bug Fixes

  • correct 1000x cache TTL inflation and purge on all admin write routes (5dc7a20)
  • correct 1000x cache TTL inflation and purge on all admin write routes (8197205)
  • load providers reliably across Node versions and module shapes (ce7215a)
  • load providers reliably across Node versions and module shapes (c403830)
  • make redis purges safe on a cluster (6ff9043)
  • make redis purges safe on a cluster (2490ac2)

Performance

  • batch cache purges instead of one round trip per key (2574d82)
  • batch cache purges instead of one round trip per key (face64d)

Refactoring

  • providers: convert both provider packages to TypeScript (#188) (c46540f)

Documentation

  • give every published package a README (#196) (2f53e09)
  • sync README with the published 5.0.1 and backfill changelogs (380997c)
  • sync README with the published 5.0.1 and backfill changelogs (9878fbb)

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from 67c53b6 to 9d33f31 Compare August 14, 2026 02:07
@derrickmehaffy derrickmehaffy mentioned this pull request Aug 14, 2026
Merged
@derrickmehaffy derrickmehaffy mentioned this pull request Aug 14, 2026
Merged
derrickmehaffy added a commit that referenced this pull request Aug 14, 2026
@derrickmehaffy @claude
chore: deduplicate the release changelog automatically
c756d12 
release-please lists the same change twice whenever a pull request was merged
with a GitHub merge commit. The merge commit carries the pull request title in
its body:

  Merge pull request #171 from strapi-community/feat/cache-dashboard

  feat: add a cache statistics endpoint for the admin dashboard

and release-please parses every conventional commit it finds in a message, so
that body line becomes an entry attributed to the merge commit while the commit
on the branch underneath produces an identical one.

There is no setting for it. BEGIN_COMMIT_OVERRIDE is keyed on the pull request,
and both commits are associated with the same one, so an override would
suppress the real entry too; `changelog-type: github` deduplicates by listing
pull requests instead of commits, but discards the conventional-commit
sections.

So this runs on every release rather than being hand-fixed once. release-please
force-updates both the release branch and the draft notes on each run, so a
manual edit would be overwritten the next time anything lands on main.

Both surfaces are covered because they are generated separately: CHANGELOG.md
on the release branch, and the draft release's own notes, which is what a
maintainer actually reads before pressing Publish.

Entries are matched on their text with the trailing ([sha](url)) stripped,
since the two copies differ only by sha, and the first occurrence wins so the
ordering is unchanged. A heading resets the comparison, so an entry that
legitimately appears under two sections is kept.

Verified against the real notes from the closed #200: 54 entries to 35, 19
duplicates removed, and a second run is a no-op.

Co-Authored-By: Claude <noreply@anthropic.com>
@derrickmehaffy derrickmehaffy mentioned this pull request Aug 14, 2026
Merged
derrickmehaffy added a commit that referenced this pull request Aug 14, 2026
@derrickmehaffy @claude
chore: deduplicate the release changelog automatically (#210)
f431962 
release-please lists the same change twice whenever a pull request was merged
with a GitHub merge commit. The merge commit carries the pull request title in
its body:

  Merge pull request #171 from strapi-community/feat/cache-dashboard

  feat: add a cache statistics endpoint for the admin dashboard

and release-please parses every conventional commit it finds in a message, so
that body line becomes an entry attributed to the merge commit while the commit
on the branch underneath produces an identical one.

There is no setting for it. BEGIN_COMMIT_OVERRIDE is keyed on the pull request,
and both commits are associated with the same one, so an override would
suppress the real entry too; `changelog-type: github` deduplicates by listing
pull requests instead of commits, but discards the conventional-commit
sections.

So this runs on every release rather than being hand-fixed once. release-please
force-updates both the release branch and the draft notes on each run, so a
manual edit would be overwritten the next time anything lands on main.

Both surfaces are covered because they are generated separately: CHANGELOG.md
on the release branch, and the draft release's own notes, which is what a
maintainer actually reads before pressing Publish.

Entries are matched on their text with the trailing ([sha](url)) stripped,
since the two copies differ only by sha, and the first occurrence wins so the
ordering is unchanged. A heading resets the comparison, so an entry that
legitimately appears under two sections is kept.

Verified against the real notes from the closed #200: 54 entries to 35, 19
duplicates removed, and a second run is a no-op.

Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@derrickmehaffy derrickmehaffy Awaiting requested review from derrickmehaffy derrickmehaffy is a code owner

Assignees

No one assigned

Labels

autorelease: pending

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@derrickmehaffy