npm Package ai@7.0.176 Hotfix Released Following 7.0.175
Is it fixed? Not yet.
Ongoing since Nov 17, 19:55 UTC. First reported Nov 17, 19:55 UTC. Not on the vendor’s status page yet.
What happened
Package ai version 7.0.176 was published shortly after version 7.0.175. Users on preceding versions are advised to check release notes and consider upgrading to patch potential issues.
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] ai@7.0.175 released 1h 14m after 7.0.174
Source
Evidence
2 reports · 2 RegistryShow
- [1]Registry First report[Hotfix] ai@7.0.175 released 1h 14m after 7.0.174(opens package registry notice in a new tab)
ai 7.0.175 was published 1h 14m after 7.0.174 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.174, check the 7.0.175 release notes and consider upgrading.
by npm registry 0upvotes 0comments
- [2]Registry[Hotfix] ai@7.0.176 released 1h 02m after 7.0.175(opens package registry notice in a new tab)
ai 7.0.176 was published 1h 02m after 7.0.175 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.175, check the 7.0.176 release notes and consider upgrading.
by npm registry 0upvotes 0comments99% match
FAQ
What happened in the npm issue?
Package ai version 7.0.176 was published shortly after version 7.0.175. Users on preceding versions are advised to check release notes and consider upgrading to patch potential issues.
What is affected by the npm issue?
npm (versions: 7.0.174, 7.0.175).
When did the npm issue start and end?
It started Nov 17, 19:55 UTC and is still ongoing (1 d 8 h so far). This page updates as it develops.
How do I get alerts for npm?
Subscribe to the npm RSS feed for every new npm incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether npm is down. npm 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 2 reports from 1 independent source.