cherrypick icon indicating copy to clipboard operation
cherrypick copied to clipboard

Published 20 hours ago • verified publisher icon kokonect-link

chore(deps): bump misskey-dev/release-manager-actions from 1 to 2

Open dependabot[bot] opened this issue 8 months ago • 0 comments

Bumps misskey-dev/release-manager-actions from 1 to 2.

Release notes

Sourced from misskey-dev/release-manager-actions's releases.

v2.0.0

2.0.0

Release Manager Actions v2 is a release support workflow based on the develop-stable branches system. It is incompatible with v1.

Migration

Migration is deprecated because it is so different from v1, but if it is necessary, do the following:

  1. Create a stable branch and register its name as a STABLE_BRANCH variable.
  2. Since ruleset management is no longer needed, remove RULESET_EDIT_APP_PRIVATE_KEY, RULESET_ID_WITHIN_RELEASE, and RULESET_ID_OUT_OF_RELEASE. Also, the rulesets used in v1 should be deleted.
  3. Grant Repository - Pull request - Read and Write permission to the GitHub App for on: release. If you don't have it, please create it.
    In the Install App tab, select org or user right ⚙️ and go to the App installation management screen, where you will see (app) is requesting an update to its permissions. [Review Request]. Select Review Request and on the next screen select Accept new permissions.
  4. Create a ruleset to protect the stable branch according to README.md.
  5. Override the three release manager workflows.
    Set line 6 of release-edit-with-push.yml to the name of the develop branch (the default branch in your repository).

Screenshots to grant permission to the app

image

image

image

v1.2.1

The copied actions need to be replaced like following:

  • Eliminated the possibility of code execution and token theft via external input

v1.2.0

The copied actions need to be replaced by the rewritten actions like this: https://github.com/misskey-dev/misskey/commit/f5d57c02c7edbf71c4f2eaff789dfd093513027d .

  • The INDENT variable allows selection of the indentation format of package.json.

v1.1.2

  • Fix: Creating Pre-release always creates rc

v1.1.0

  • Make it possible to specify the app when creating a release, so that the on: release workflow can be triggered.

1.0.2

... (truncated)

Changelog

Sourced from misskey-dev/release-manager-actions's changelog.

CHANGELOG

2.0.1

  • Removed unnecessary secrets (RULESET_...)

2.0.0

Release Manager Actions v2 is a release support workflow based on the develop-stable branches system. It is incompatible with v1.

Migration

Migration is deprecated because it is so different from v1, but if it is necessary, do the following:

  1. Create a stable branch and register its name as a STABLE_BRANCH variable.
  2. Since ruleset management is no longer needed, remove RULESET_EDIT_APP_PRIVATE_KEY, RULESET_ID_WITHIN_RELEASE, and RULESET_ID_OUT_OF_RELEASE. Also, the rulesets used in v1 should be deleted.
  3. Grant Repository - Pull request - Read and Write permission to the GitHub App for on: release. If you don't have it, please create it.
    In the Install App tab, select org or user right ⚙️ and go to the App installation management screen, where you will see (app) is requesting an update to its permissions. [Review Request]. Select Review Request and on the next screen select Accept new permissions.
  4. Create a ruleset to protect the stable branch according to README.md.
  5. Override the three release manager workflows.
    Set line 6 of release-edit-with-push.yml to the name of the develop branch (the default branch in your repository).

1.2.1

The copied actions need to be replaced like following:

  • Eliminated the possibility of code execution and token theft via external input

1.2.0

The copied actions need to be replaced by the rewritten actions like this: https://github.com/misskey-dev/misskey/commit/f5d57c02c7edbf71c4f2eaff789dfd093513027d .

  • The INDENT variable allows selection of the indentation format of package.json.

1.1.2

  • Fix: Creating Pre-release always creates rc

1.1.1

  • Fix: release-with-ready not creating releases in external apps

1.1.0

  • Make it possible to specify the app when creating a release, so that the on: release workflow can be triggered.

1.0.0

  • The first release
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

dependabot[bot] avatar Jun 03 '24 18:06 dependabot[bot]