-
Notifications
You must be signed in to change notification settings - Fork 15
chore(main): release 3.0.0 #379
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.
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
serhalp
merged 2 commits into
main
from
release-please--branches--main--components--angular-runtime
Aug 14, 2025
Merged
chore(main): release 3.0.0 #379
serhalp
merged 2 commits into
main
from
release-please--branches--main--components--angular-runtime
Aug 14, 2025
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
token-generator-app
bot
requested a review
from a team
as a code owner
August 14, 2025 18:32
β Deploy Preview for angular-runtime-demo ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
@github-actions
github-actions
bot
added
the
type: chore
work needed to keep the product and development running smoothly
label
Aug 14, 2025
@token-generator-app
token-generator-app
bot
changed the title
(ει€) chore(main): release 2.5.0 (ει€γγγΎγ§)
(θΏ½θ¨) chore(main): release 3.0.0 (θΏ½θ¨γγγΎγ§)
Aug 14, 2025
@token-generator-app
token-generator-app
bot
force-pushed
the
release-please--branches--main--components--angular-runtime
branch
from
August 14, 2025 19:21
1def2ce to
c940294
Compare
serhalp
serhalp
approved these changes
Aug 14, 2025
@serhalp
serhalp
deleted the
release-please--branches--main--components--angular-runtime
branch
August 14, 2025 19:55
@token-generator-app
token-generator-app
bot
added
autorelease: tagged
and removed
autorelease: pending
labels
Aug 14, 2025
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.
Uh oh!
There was an error while loading. Please reload this page.
π€ 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.