Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable releasing packages from feature branches #14472

Closed
pomek opened this issue Jun 27, 2023 · 1 comment · Fixed by #14473
Closed

Enable releasing packages from feature branches #14472

pomek opened this issue Jun 27, 2023 · 1 comment · Fixed by #14473
Assignees
Labels
squad:platform Issue to be handled by the Platform team. type:task This issue reports a chore (non-production change) and other types of "todos".

Comments

@pomek
Copy link
Member

pomek commented Jun 27, 2023

Provide a description of the task

So far, the release scripts can be executed while the git repository is checked out to the #release branch.

However, we would like to enable releasing the code from feature branches, e.g., when preparing an alpha release, it could be performed from a feature branch containing an experimental feature.

Scope

  • Allow generating the changelog and preparing packages to release from a custom branch.
    • The branch name could be specified via CLI, e.g., --branch alpha.
  • Allow defining the latest release tag when generating the changelog. It can be useful when performing two alpha releases from different branches. By default, the tool uses a tag based on a version field in a package.json file.
    • When preparing an x.y.z-alpha.1 release, we should note that it is an update from x.y.z-alpha.0 instead of x.y.z.
    • The generator accepts the from option.
@pomek pomek added type:task This issue reports a chore (non-production change) and other types of "todos". squad:platform Issue to be handled by the Platform team. labels Jun 27, 2023
@pomek pomek self-assigned this Jun 27, 2023
@CKEditorBot CKEditorBot added status:planned Set automatically when an issue lands in the "Sprint backlog" column. We will be working on it soon. status:in-progress Set automatically when an issue lands in the "In progress" column. We are working on it. and removed status:planned Set automatically when an issue lands in the "Sprint backlog" column. We will be working on it soon. labels Jun 27, 2023
@pomek
Copy link
Member Author

pomek commented Jun 27, 2023

All required PRs are mentioned above. (☝️)

psmyrek added a commit to ckeditor/ckeditor5-dev that referenced this issue Jun 27, 2023
Other (release-tools): The `generateChangelogForMonoRepository()` and `generateChangelogForSinglePackage()` tasks use a value from the optional `from` option when mentioning a current version of packages. See ckeditor/ckeditor5#14472.
psmyrek added a commit that referenced this issue Jun 27, 2023
Internal: Release tools - enable execution from feature branches by specifying the `--branch` name. Closes #14472.
@CKEditorBot CKEditorBot removed the status:in-progress Set automatically when an issue lands in the "In progress" column. We are working on it. label Jun 27, 2023
@CKEditorBot CKEditorBot added this to the iteration 65 milestone Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
squad:platform Issue to be handled by the Platform team. type:task This issue reports a chore (non-production change) and other types of "todos".
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants