Repository navigation
Release: use correct build date in release verification - #5521
Merged
Merged
Conversation
timmywil
commented
Jul 17, 2024
timmywil
commented
Jul 17, 2024
mgol
approved these changes
Jul 17, 2024
mgol
left a comment
Member
There was a problem hiding this comment.
One suggestion. LGTM overall, though.
timmywil
force-pushed
the
release
branch
5 times, most recently
from
July 18, 2024 00:56
20af991 to
0590747
Compare
timmywil
commented
Jul 18, 2024
| } | ||
| console.log(); | ||
| for ( const file of mismatchingFiles ) { | ||
| console.log( `❌ ${ file }` ); |
Member
Author
There was a problem hiding this comment.
These characters do seem to print fine in GH actions.
Sample: https://github.com/timmywil/jquery/actions/runs/9983672787/job/27591642443
As expected, the files with a date fail, but the min and map files pass.
Member
Author
|
I was debugging the workflow a bit on my fork and made a couple tweaks:
|
2 tasks done
mgol
approved these changes
Jul 19, 2024
mgol
left a comment
Member
There was a problem hiding this comment.
Minor remarks to address, otherwise LGTM
timmywil
added a commit
to timmywil/jquery
that referenced
this pull request
Jul 23, 2024
- the date is actually the date of the commit *prior* to the tag commit, as the files are built and then committed. - also, the CDN should still be checked for non-stable releases, and should use different filenames (including in the map files). - certain files should be skipped when checking the CDN. - removed file diffing because it ended up being far too noisy, making it difficult to find the info I needed. - because the build script required an addition, release verification will not work until the next release. - print all files in failure case and whether each matched - avoid npm script log in GH release notes changelog - exclude changelog.md from release:clean command - separate the post-release script from release-it for now, so we can keep manual verification before each push. The exact command is printed at the ened for convenience. Close jquerygh-5521
timmywil
added a commit
to timmywil/jquery
that referenced
this pull request
Jul 23, 2024
timmywil
added a commit
to timmywil/jquery
that referenced
this pull request
Jul 24, 2024
- the date is actually the date of the commit *prior* to the tag commit, as the files are built and then committed. - also, the CDN should still be checked for non-stable releases, and should use different filenames (including in the map files). - certain files should be skipped when checking the CDN. - removed file diffing because it ended up being far too noisy, making it difficult to find the info I needed. - because the build script required an addition, release verification will not work until the next release. - print all files in failure case and whether each matched - avoid npm script log in GH release notes changelog - exclude changelog.md from release:clean command - separate the post-release script from release-it for now, so we can keep manual verification before each push. The exact command is printed at the ened for convenience. Closes jquerygh-5521
timmywil
added a commit
to timmywil/jquery
that referenced
this pull request
Jul 24, 2024
mgol
approved these changes
Jul 26, 2024
- the date is actually the date of the commit *prior* to the tag commit, as the files are built and then committed. - also, the CDN should still be checked for non-stable releases, and should use different filenames (including in the map files). - certain files should be skipped when checking the CDN. - removed file diffing because it ended up being far too noisy, making it difficult to find the info I needed. - because the build script required an addition, release verification will not work until the next release. - print all files in failure case and whether each matched - avoid npm script log in GH release notes changelog - exclude changelog.md from release:clean command - separate the post-release script from release-it for now, so we can keep manual verification before each push. The exact command is printed at the ened for convenience. Closes jquerygh-5521
timmywil
added a commit
that referenced
this pull request
Jul 29, 2024
- the date is actually the date of the commit *prior* to the tag commit, as the files are built and then committed. - also, the CDN should still be checked for non-stable releases, and should use different filenames (including in the map files). - certain files should be skipped when checking the CDN. - removed file diffing because it ended up being far too noisy, making it difficult to find the info I needed. - because the build script required an addition, release verification will not work until the next release. - print all files in failure case and whether each matched - avoid npm script log in GH release notes changelog - exclude changelog.md from release:clean command - separate the post-release script from release-it for now, so we can keep manual verification before each push. The exact command is printed at the ened for convenience. Closes gh-5521
timmywil
added a commit
that referenced
this pull request
Jul 29, 2024
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Checklist