7b4052470b
- Allow to configure multiple branches to release from - Allow to define a distribution channel associated with each branch - Manage the availability on distribution channels based on git merges - Support regular releases, maintenance releases and pre-releases - Add the `addChannel` plugin step to make an existing release available on a different distribution channel BREAKING CHANGE: the `branch` option has been removed in favor of `branches` The new `branches` option expect either an Array or a single branch definition. To migrate your configuration: - If you want to publish package from multiple branches, please the configuration documentation - If you use the default configuration and want to publish only from `master`: nothing to change - If you use the `branch` configuration and want to publish only from one branch: replace `branch` by `branches` (`"branch": "my-release-branch"` => `"branches": "my-release-branch"`)
18 lines
502 B
Markdown
18 lines
502 B
Markdown
# Recipes
|
|
|
|
## CI configurations
|
|
- [CircleCI 2.0 workflows](circleci-workflows.md)
|
|
- [Travis CI](travis.md)
|
|
- [Travis CI with build stages](travis-build-stages.md)
|
|
- [GitLab CI](gitlab-ci.md)
|
|
|
|
## Git hosted services
|
|
- [Git authentication with SSH keys](git-auth-ssh-keys.md)
|
|
|
|
## Release workflow
|
|
- [Publishing on distribution channels](distribution-channels.md)
|
|
- [Publishing maintenance releases](maintenance-releases.md)
|
|
- [Publishing pre-releases](pre-releases.md)
|
|
|
|
## Package managers and languages
|