ci(deserializer): add GHA for NPM publishing#420
Merged
TartanLeGrand merged 6 commits intodevelopfrom Jun 11, 2025
Merged
Conversation
TartanLeGrand
commented
Jun 11, 2025
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
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.
This pull request includes significant changes to the CI/CD pipeline for the
dataprotector-deserializerpackage. The most important changes involve the removal of the existing Drone CI configuration and the addition of a new GitHub Actions workflow for publishing the package to NPM.Pipeline and workflow changes:
.drone.yml: Removed the entire Drone CI configuration for building, testing, and publishing thedataprotector-deserializerpackage.github/workflows/publish-npm-deserializer.yml: Added a new GitHub Actions workflow to handle the publishing of thedataprotector-deserializerpackage to NPM, supporting bothlatestandnightlytags.