chore(main): release 3.0.0 #379
Merged
Conversation
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
![token-generator-app[bot]](https://avatars.githubusercontent.com/u/7892489?s=60&v=4){kind=small}
✅ Deploy Preview for angular-runtime-demo ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
bot
added
the
type: chore
token-generator-app
bot
changed the title
token-generator-app
bot
force-pushed
the
release-please--branches--main--components--angular-runtime
branch
from
1def2ce to
c940294
Compare
serhalp
approved these changes
Aug 14, 2025
serhalp
deleted the
release-please--branches--main--components--angular-runtime
branch
|
🤖 Created releases: 🌻 |
token-generator-app
bot
added
autorelease: tagged
and removed
autorelease: pending
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🤖 I have created a release beep boop
3.0.0 (2025-08-14)
⚠ POTENTIALLY BREAKING CHANGES
You can now set cache headers on responses when using SSR. See https://docs.netlify.com/build/caching/caching-overview/ for the full set of features.
This is marked as potentially breaking because previously, per Netlify Edge Function caching behavior, cache response headers were ignored, and after this change they will be respected. It's unlikely this will affect you.
Features
This PR was generated with Release Please. See documentation.