craft
craft copied to clipboard
The universal Sentry release CLI 🚀
The GitHub target should never need to hold full release assets (nor any other potentially large files) in memory. This issue tracks replacing code that reads full files from disk,...
We may improve debugability by using `--keep-names` and perhaps other goodies, see: - https://github.com/getsentry/craft/pull/326#issuecomment-974122844 - https://github.com/atombrenner/stack-trace - https://github.com/evanw/node-source-map-support
similar to https://github.com/getsentry/sentry-java/blob/main/CONTRIBUTING.md and other SDKs so we know which command to build and run locally in case we want to debug/test it commands that should be there: yarn install...
I would prefer to run craft without debug logs on the console. Especially when publishing to crates.io, the output is enormously large. When errors occur, it would still be great...
Sometimes, when Craft is faster than GitHub and status check integrations, Craft cannot find any relevant checks, even in pending state and immediately fails: https://github.com/getsentry/onpremise/runs/777959403?check_suite_focus=true We should figure out a...
When preparing a release, validate the new release number by checking if there's a release that might be called "previous". Example: when we're releasing version `1.2.4`, `1.2.3` should _probably_ exist.
For generic HTTP errors, it would be better to print additional information, rather than: ``` ✖ error HttpError at response.text.then.message (/Users/jauer/.config/yarn/global/node_modules/@octokit/rest/lib/request/request.js:72:19) at process._tickCallback (internal/process/next_tick.js:68:7) ``` Desirable user information (INFO log...
@bitsandfoxes reported that `craft publish` fails at the very end (after all targets succeed) if the repo is in a dirty state. We should either detect this earlier and bail...
https://github.com/marketplace/actions/release-drafter Possible course of action is to add an option to pull the changelog from the draft release instead of reading it from a file. One concern with using release...
As proposed by @mitsuhiko. More information: https://devblogs.microsoft.com/commandline/windows-package-manager-preview/?WT.mc_id=ITOPSTALK-reddit-abartolo