Repository navigation
fix: support current artifact protocol and explicit strict validation - #1
Merged
Merged
Conversation
Zxilly
marked this pull request as ready for review
October 7, 2026 09:27
This was referenced Oct 7, 2026
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
1 participant
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.
Repair the shared test-server helper used by the ZNotify SDK workflows. Artifact v3 uploads are retired, and the old artifact client can silently fall back to an older release instead of testing the candidate server.
This draft adds artifact v4 support through @actions/artifact 2.3.2 and an explicit require-current-artifact input (default false). Standalone SDK release fallback is preserved; strict callers fail closed. Node 24 matches the resolved dependency engine requirements.
Local validation: immutable install, six artifact-policy unit tests, typecheck, reproducible bundles, and real bundled strict-missing/no-PID cleanup checks pass. Source, generated bundles and matching workflow tests are being uploaded before this draft is marked ready. Remote three-platform artifact/release validation is required before merge.