chore: release 8.0.0-rc.0#253
Merged
damienwebdev merged 2 commits intomainfrom May 10, 2026
Merged
Conversation
447e636 to
1a1da57
Compare
41b75bd to
9b2b216
Compare
f775ce6 to
df86fdf
Compare
c7e8bc6 to
28bd4a4
Compare
d71102c to
a844df6
Compare
04572a3 to
1bbf212
Compare
109a123 to
70a81a1
Compare
2e019f2 to
6a8d490
Compare
Contributor
Author
|
🤖 Created releases: 🌻 |
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
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
8.0.0-rc.0 (2026-05-10)
⚠ BREAKING CHANGES
cache-magentowe need to keep magento inside the GITHUB_WORKSPACE (the root repo). We now do this in the_ghamagentofolder. If you rely on thesteps.setup-magento.outputs.pathnothing changes for you. But, if you hardcoded the path, it's likely broken.Features
Bug Fixes
This PR was generated with Release Please. See documentation.