Skip to content

Release: use correct build date in release verification - #5521

Merged
timmywil merged 3 commits into
jquery:mainfrom
timmywil:release
Jul 29, 2024
Merged

timmywil merged 3 commits into
jquery:mainfrom
timmywil:release

Conversation

@timmywil

Copy link
Copy Markdown
Member

Summary

  • 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.

Checklist

@timmywil timmywil added this to the 4.0.0 milestone Jul 17, 2024
@timmywil
timmywil requested a review from mgol July 17, 2024 21:20
Comment thread .gitignore
Comment thread .release-it.cjs

@mgol mgol left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One suggestion. LGTM overall, though.

Comment thread build/release/verify.js Outdated
@timmywil
timmywil force-pushed the release branch 5 times, most recently from 20af991 to 0590747 Compare July 18, 2024 00:56
Comment thread build/release/verify.js
}
console.log();
for ( const file of mismatchingFiles ) {
console.log( `❌ ${ file }` );

@timmywil timmywil Jul 18, 2024 •

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@timmywil

timmywil commented Jul 18, 2024 •

Copy link
Copy Markdown
Member Author

I was debugging the workflow a bit on my fork and made a couple tweaks:

  • fixed an issue with the build in GH actions where setting the env option in the exec() was overriding the PATH variable. This seemed to only affect Linux.
  • if the build is not reproducible, print all files and whether each matched. See my other comment for a sample.
  • called the node script directly from release-it to avoid the npm script log in GH release notes (which I manually removed this time)
  • excluded changelog.md from release:clean, which is now committed
  • separated the post release script from release-it for now. This is so we can keep manual verification before each push. The exact post-release command is printed at the end of the release for convenience.

@mgol mgol left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor remarks to address, otherwise LGTM

Comment thread .release-it.cjs
Comment thread build/release/verify.js Outdated
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
@timmywil
timmywil requested a review from mgol July 24, 2024 15:27

@mgol mgol left a comment •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks mostly good, I have some minor comments. Nice work!

Comment thread .husky/commit-msg
Comment thread build/release/verify.js Outdated
timmywil added 3 commits July 29, 2024 12:23
- 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
timmywil merged commit a7d3383 into jquery:main Jul 29, 2024
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
@timmywil
timmywil deleted the release branch July 29, 2024 16:34
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Sep 24, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Development

Successfully merging this pull request may close these issues.

2 participants