-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add test on shortname continuity #1195
Comments
tidoust
added a commit
that referenced
this issue
Feb 6, 2024
That was missed in the update that changed their shortname. This affected Specref, see: tobie/specref#777 Also see #1195 for detecting the problem before a new index gets released.
tidoust
added a commit
that referenced
this issue
Feb 6, 2024
) That was missed in the update that changed their shortname. This affected Specref, see: tobie/specref#777 Also see #1195 for detecting the problem before a new index gets released.
tidoust
added a commit
that referenced
this issue
Jun 25, 2024
This validates that shortnames present in the latest published version of web-specs will continue to exist in the upcoming version, either as shortnames or as former names. Fixes #1195 with help from Vital, thx!
tidoust
added a commit
that referenced
this issue
Jun 26, 2024
This validates that shortnames present in the latest published version of web-specs will continue to exist in the upcoming version, either as shortnames or as former names. Fixes #1195 with help from Vital, thx!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the addition of the
formerNames
property (see #1066), we can now track specs whose shortname changes. But then we don't have any test that checks on shortname continuity between the latest commit and the latest published version of web-specs. We should have one to make sure that we don't forget to complete theformerNames
property as needed.The text was updated successfully, but these errors were encountered: