chore: use node24 only in publish job #3027
Merged
Conversation
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
|
ShadowCat567
approved these changes
Oct 24, 2025
osama-rizk
pushed a commit
that referenced
this pull request
Oct 28, 2025
Currently publish is failing with: ```console Failed to restore cache entry. Exiting as fail-on-cache-miss is set. Input key: Linux-4c7d643f27f6e81e93c730d8c8f60cf1808038aee3c97303cbad98bbf8f4b29b-node24-cdklibFROM_PACKAGE_LOCK ``` We suspect the switch to node 24 in the restore cache step is messing it up. --------- Co-authored-by: Vieltojarvi <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Currently publish is failing with:
Failed to restore cache entry. Exiting as fail-on-cache-miss is set. Input key: Linux-4c7d643f27f6e81e93c730d8c8f60cf1808038aee3c97303cbad98bbf8f4b29b-node24-cdklibFROM_PACKAGE_LOCKWe suspect the switch to node 24 in the restore cache step is messing it up.