Bump dayjs to latest patch (~1.11.21) (#743)#1076
Merged
Merged
Conversation
carrythebanner
approved these changes
Jul 10, 2026
carrythebanner
left a comment
carrythebanner
left a comment
Collaborator
There was a problem hiding this comment.
Thanks for digging into this @dduugg!
The original issue was a bit vague; I should have clarified that Day.js is also used in a 3rd place, on /calendar/ pages. (The 2 changes here are for the backend and the "beta" cal frontend.) The /calendar/ pages use a version of the library embedded in /site/themes/s2b_hugo_theme/static/lib/; that one is still on v1.11.10. We can definitely merge this but it would also be good to update the other one, too.
Collaborator
|
I'll file a separate PR for the remaining bit. |
Collaborator
|
For remaining front-end (still needs testing): #1079 |
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.
Closes #743.
Day.js is already at the latest published patch, 1.11.21 (npm has nothing newer in the 1.11.x line or beyond), and
package-lock.jsonalready resolves to it. The only thing lagging was the declared floor in the two workspace manifests, which still read~1.11.13.This bumps the
dayjsrange to~1.11.21in bothapp/package.jsonandcal/package.jsonso the manifests reflect the current patch. The lockfile needed no change (already synced), andnpm installconfirmed that.No runtime change: the installed dayjs version is identical before and after, so this only aligns the manifest floors with the already-current lockfile.