Skip to content

Conversation

@kamilogorek
Copy link
Contributor

@kamilogorek kamilogorek commented Jul 22, 2021

  • update sentry-cli to 1.67.2
  • add support for new stripCommonPrefix, ignoreMissing and ignoreOptions options
  • rename validate.ts to options.ts as its actually fetching options, not only validating them
  • refactor getShouldFinalize to a generic getBooleanOption
  • remove custom TS types and use real ones from sentry-cli

Fixes #41
Fixes #59
Fixes #53

Copy link
Member

@AbhiPrasad AbhiPrasad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ but will leave final approval rights to Ecosystem team.

|`environment`|Set the environment for this release. E.g. "production" or "staging". Omit to skip adding deploy to release.|-|
|`finalize`|When false, omit marking the release as finalized and released.|`true`|
|`ignore_missing`|When the flag is set and the previous release commit was not found in the repository, will create a release with the default commits count instead of failing the command.|`false`|
|`ignore_empty`|When the flag is set, command will not fail and just exit silently if no new commits for a given release have been found.|`false`|
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Feels bad to duplicate this between the README and action.yml, but I realized that there are slight differences between the readme and this (for ex, version defaults to {{github.sha}}, but there is not default field in yml for that key).

default: true
ignore_missing:
description: 'When the flag is set and the previous release commit was not found in the repository, will create a release with the default commits count instead of failing the command.'
required: false
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ignore_missing and ignore_empty default to false. Do we have to update the action.yml to add a default: true for these fields?

Copy link
Contributor Author

@kamilogorek kamilogorek Jul 22, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't, as we do that here https://github.com/getsentry/action-release/pull/63/files#diff-4fab5baaca5c14d2de62d8d2fceef376ddddcc8e9509d86cfa5643f51b89ce3dR15-R16
And when not specified in the action.yml, they'll be undefined, thus if (!option) branch will return defaultValue

Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
Copy link
Contributor

@mgaeta mgaeta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great 👍🏽

@kamilogorek kamilogorek merged commit 62ef65f into master Jul 23, 2021
@kamilogorek
Copy link
Contributor Author

@scefali @mgaeta could one of you perform a new release please? Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Upgrade to latest CLI Allow setting stripCommonPrefix Could not find the SHA of the previous release

5 participants