Astro 7.4.10 Released Rapidly Following 7.4.9 Patch
Is it fixed? Not yet.
Ongoing since Nov 10, 20:11 UTC. First reported Nov 10, 20:11 UTC.
What happened
Astro version 7.4.10 was published shortly after 7.4.9 to address potential issues in the previous release. Developers currently using version 7.4.9 are advised to check the release notes and upgrade.
What caused it?
Under active investigation. No report has identified a root cause yet.
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Official fixTimeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on package registry notice
[Hotfix] astro@7.4.10 released 1h 36m after 7.4.9
Source
Evidence
3 reports · 3 RegistryShow
- [1]Registry First report[Hotfix] astro@7.4.10 released 1h 36m after 7.4.9(opens package registry notice in a new tab)
astro 7.4.10 was published 1h 36m after 7.4.9 in the same 7.4 line. A follow-up this fast usually patches a problem in the previous release: if you are on 7.4.9, check the 7.4.10 release notes and consider upgrading.
by npm registry 0upvotes 0comments
- [2]Registry[Hotfix] ai@6.0.329 released 2h 27m after 6.0.328(opens package registry notice in a new tab)
ai 6.0.329 was published 2h 27m after 6.0.328 in the same 6.0 line. A follow-up this fast usually patches a problem in the previous release: if you are on 6.0.328, check the 6.0.329 release notes and consider upgrading. The current latest release is 7.0.169.
by npm registry 0upvotes 0comments94% match
- [3]Registry[Hotfix] ai@7.0.169 released 2h 29m after 7.0.168(opens package registry notice in a new tab)
ai 7.0.169 was published 2h 29m after 7.0.168 in the same 7.0 line. A follow-up this fast usually patches a problem in the previous release: if you are on 7.0.168, check the 7.0.169 release notes and consider upgrading.
by npm registry 0upvotes 0comments98% match
FAQ
What happened in this issue?
Astro version 7.4.10 was published shortly after 7.4.9 to address potential issues in the previous release. Developers currently using version 7.4.9 are advised to check the release notes and upgrade.
What is affected by this issue?
Versions: 7.4.9.
When did this issue start and end?
It started Nov 10, 20:11 UTC and is still ongoing (8 d 8 h so far). This page updates as it develops.
How do I get alerts for incidents like this?
Subscribe to the WhatBrokeToday RSS feed for every new incident, or connect an AI assistant over MCP. All incidents feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 3 reports from 1 independent source.