-
Notifications
You must be signed in to change notification settings - Fork 50
π¦ Release browser-specs@3.6.0 #574
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
Conversation
20e8cfd to
f7e937f
Compare
dontcallmedom
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure why it is picking https://w3c.github.io/reporting/network-reporting in preference to https://w3c.github.io/reporting/ ; both are probably relevant (and the former should be checked for addition to browser-specs), but the current entry for reporting should not be replaced by network-reporting
That comes from /TR. Something broken over there? https://www.w3.org/TR/reporting-1/ now returns the Network Reporting API in particular. Ping @deniak @jennyliang220 (Edit: That's probably a bad auto-publish config in the reporting repo. I see recent commits to fix that: https://github.com/w3c/reporting/commits/main) |
f7e937f to
8b79c8c
Compare
|
Problem fixed for the Reporting API. That was a bad auto-publication config, indeed. |
|
there are still some leftover of the network reporting API in the diff above - is that expected? |
|
Apparently, the W3C API didn't like the spec hiccup, and continues to return the wrong title and ED URL. @deniak, see https://api.w3.org/specifications/reporting-1 |
This should be fixed. Echidna doesn't expect the ED and title to change when republishing a document on the same day but that's probably a mistake. I created an issue and will try to tackle it soon. |
8b79c8c to
6f2d53d
Compare
β NEVER add commits to this pull request.
π€ This pull request was automatically created to facilitate human review of
browser-specschanges based on list of specs at 9cd9e3d.π§ Please review the diff below and version numbers. If all looks good, merge this pull request to release the changes to npm.
π¦ Latest released
browser-specspackage was v3.5.1. Merging this pull request will release v3.6.0. Make sure that the bump is the right one for the changes.β If any change needs to be made before release, do not add a commit to this pull request. Changes should rather be handled in a separate pull request and pushed to the main branch. You may leave this pull request open in the meantime, or close it. The pre-release job will automatically update this pull request or create a new one once the updates have made their way to the main branch.
π The actual change introduced by this pull request is a version bump in
packages/browser-specs/package.json. You do not need to review that change. The bumped version is not the version that will be released when this pull request is merged, but rather the version that will be released next time.