[dx] Allow to publish on the dev channel #258
Open
+127
−29
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.
Add Multi-Channel Publishing Support to GitHub Actions Workflow
Summary
This PR enhances the NPM publish workflow to support publishing packages to different NPM distribution channels (
latestanddev), enabling development releases and pre-releases without affecting the stable release channel.Changes
Workflow Dispatch Inputs
Added two new input parameters for manual workflow triggers:
channel(required, default:dev):latestordevversion(optional):latestchannel on master branchValidation Rules
Branch Restriction: The
latestchannel can only be published from themasterbranchdevchannel can be published from any branchVersion Override Restriction: Custom version cannot be provided when publishing to
latestchannel frommasterbranchlatestchannel on master, the version from package.json must be usedlatestdev) can use custom versionsVersion Format Validation: For
devchannel publishes, enforces version formatX.Y.Z-dev.N3.0.9-dev.0,3.0.9-dev.1, etc.Publishing Logic
devchannel: Publishes with--tag devflagnpm install @datadog/webpack-plugin@devlatestchannel: Publishes without tag (default latest)npm install @datadog/webpack-pluginLogging Updates
channelfield for better observabilityUsage Examples
Publish development release from feature branch
3.0.9-dev.0in your branchchannel:devversion:3.0.9-dev.0(or leave empty to use current version)Publish stable release from master
masterbranchbump.yamlfor it)channel:latestversion: leave empty (will use package.json version)Publish dev release from master with custom version
masterbranchchannel:devversion:3.0.9-dev.0(custom version allowed for non-latest channels)Automatic release (unchanged)
latestchannel by default