Bumped Astro#298
Merged
Merged
Conversation
Deploying framework-tracker with
|
| Latest commit: |
6d81367
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6e61ec88.framework-tracker.pages.dev |
| Branch Preview URL: | https://astro-5-17-3.framework-tracker.pages.dev |
43081j
approved these changes
Jul 19, 2026
43081j
left a comment
43081j
left a comment
Contributor
There was a problem hiding this comment.
Looks good 👍
Minor note: this means we have multiple esbuild versions installed in the monorepo. May be worth figuring out which deps are pulling the old one in and updating those too. That may happen naturally as we update the rest though
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
2 participants
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.
Astro needs to be bumped through all its major and minor updates before I can turn daily updates on for the package. That is about 9 PRs to get to latests.
I have also updated the wording and added a new section for the start project so each one lists how it was set up.
This will also let me know if my versioning works correctly. Each new version should create a new file in the repo with stats. I wonder if stat changes should link the PRs so you know what the full package.json was like or store it in the stats themselves?