-
Notifications
You must be signed in to change notification settings - Fork 105
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
(CONT-1026) Deprecate release command set #1251
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chelnak
force-pushed
the
CONT-1026-deprecate_release_commands
branch
from
May 30, 2023 12:05
cb27e3c
to
2383a46
Compare
chelnak
force-pushed
the
CONT-1026-deprecate_release_commands
branch
from
May 30, 2023 12:33
2383a46
to
1cd80d0
Compare
chelnak
changed the title
Cont 1026 deprecate release commands
(CONT-1026) Deprecate release command set
May 30, 2023
chelnak
force-pushed
the
CONT-1026-deprecate_release_commands
branch
from
June 13, 2023 12:55
1cd80d0
to
4281655
Compare
chelnak
force-pushed
the
CONT-1026-deprecate_release_commands
branch
2 times, most recently
from
June 20, 2023 15:13
394a5f9
to
e2c3f0f
Compare
The release prep command introduces a dependency on the github-changelog-generator gem which is unmaintained and broken. This ticket exists primarily to remove this command but that introduces an unnecessary level of commands for users. For example ``` pdk release pdk release prep pdk release publish ``` This change deprecates the `release` command set. They will be removed in a future version.
To reduce complexity, this change introduces a new `publish` top-level command. The intention is to replace `pdk release` and `pdk release publish`
chelnak
force-pushed
the
CONT-1026-deprecate_release_commands
branch
from
June 23, 2023 08:56
f0f3ed8
to
cb092b7
Compare
chelnak
force-pushed
the
CONT-1026-deprecate_release_commands
branch
from
June 23, 2023 09:07
cb092b7
to
23b51a8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The release prep command introduces a dependency on the
github-changelog-generator
gem which is unmaintained and broken.This PR exists primarily to remove this command but that introduces an unnecessary level of commands for users. For example
Additionally as part of this ticket, we lift up the publish command to the root level so we have the following:
pdk publish
Due to the fact that
pdk publish
now has the single responsibility of publishing to the forge,pdk build
has been changed to perform some pre-build checks, much like the old release command did.By default,
pdk build
will nowEach step can be skipped by using the respective flag:
--skip-validation
--skip-documentation