Revert marking JSON Parse with Source as discontinued#2323
Merged
Conversation
Not yet merged in main spec, see also #2319 (comment)
tidoust
approved these changes
Jan 28, 2026
|
Thank you! Would you consider releasing this as web-specs 3.77.1 before the end of the week? No worries if not, then we would address this in BCD. |
Member
|
Yes but we need to tweak the data some more unfortunately. "discontinued" was meant to be a somewhat definitive status. Once a spec switches to "discontinued", the build code simply reuses the information from the latest published version, regardless of what the source list says... Will look into it when I have a minute, sorry for the delay! |
tidoust
added a commit
that referenced
this pull request
Jan 29, 2026
We flagged the entry as "discontinued" by mistake and released a version of web-specs with that status. The build code now takes that released information as granted. This is a good mechanism in general as discontinued specs tend to disappear over time. This does not help however when we make a mistake and need to change the standing again. This update makes the "good" standing explicit for the spec to prevent the build from using the discontinued info. We can rollback that change once we publish a new version of web-specs where the spec is no longer discontinued. Via #2323 (comment)
tidoust
added a commit
that referenced
this pull request
Jan 29, 2026
We flagged the entry as "discontinued" by mistake and released a version of web-specs with that status. The build code now takes that released information as granted. This is a good mechanism in general as discontinued specs tend to disappear over time. This does not help however when we make a mistake and need to change the standing again. This update makes the "good" standing explicit for the spec to prevent the build from using the discontinued info. We can rollback that change once we publish a new version of web-specs where the spec is no longer discontinued. Via #2323 (comment)
Member
|
Now done and released in the latest version of web-specs. I see our misadventure prompted TC39 to update the description in the finished proposals document. I'll check things more thoroughly next time instead of relying on this list alone. |
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
3 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.
Not yet merged in main spec, see also #2319 (comment)