Skip to content

feat: Add gem target#119

Merged
HazAT merged 6 commits intomasterfrom
feat/gem-target
Aug 20, 2020
Merged

feat: Add gem target#119
HazAT merged 6 commits intomasterfrom
feat/gem-target

Conversation

@HazAT
Copy link
Member

@HazAT HazAT commented Aug 14, 2020

I successfully did released https://github.com/getsentry/raven-ruby/releases/tag/3.0.2 with this branch.

➜ node ~/Projects/craft/dist/index.js publish 3.0.2
ℹ info craft 0.10.1
ℹ info "craft" version is compatible with the minimal version from the configuration file.
ℹ info Publishing version: "3.0.2"
ℹ info Using "GithubStatusProvider" for status checks
ℹ info Using "ZeusArtifactProvider" for artifacts
ℹ info No config provided for Github status provider, calculating the combined status...
ℹ info Revision df427b7320d36f30975d6746f730b1d12316bbf6 has been built successfully.
ℹ info
ℹ info Available artifacts:
┌────────────────────────┬─────────┬──────────────────────────────────┬─────────────────────┐
│ File Name              │ Size    │ Updated                          │ ContentType         │
├────────────────────────┼─────────┼──────────────────────────────────┼─────────────────────┤
│ sentry-raven-3.0.2.gem │ 46.5 kB │ 2020-08-20T10:11:00.038860+00:00 │ application/tar+gem │
└────────────────────────┴─────────┴──────────────────────────────────┴─────────────────────┘

ℹ info Publishing to targets:
ℹ info   - gem
ℹ info   - github
ℹ info   - registry
ℹ info
? Is everything OK? Type "yes" to proceed: yes
ℹ info
ℹ info =================================
ℹ info === Publishing to target: gem ===
ℹ info =================================
ℹ info [gem] › Pushing gem "sentry-raven-3.0.2.gem"
ℹ info [gem] › Successfully registered gem
ℹ info
ℹ info ====================================
ℹ info === Publishing to target: github ===
ℹ info ====================================
ℹ info [github] › Target "github": publishing version "3.0.2"...
ℹ info [github] › Git tag: "3.0.2"
ℹ info [github] › Creating a new release for tag "3.0.2"
ℹ info [github] › Uploading asset "sentry-raven-3.0.2.gem" to getsentry/raven-ruby:3.0.2
❯ log [github] › Uploaded asset "sentry-raven-3.0.2.gem".
ℹ info
ℹ info ======================================
ℹ info === Publishing to target: registry ===
ℹ info ======================================
ℹ info [registry] › Cloning "https://github.com/getsentry/sentry-release-registry/" to "/var/folders/7d/4fxc2_s94_z6ygyf5yk74t700000gn/T/craft-release-registry-v1HQuZ"...
ℹ info [registry] › Adding the version file to the registry for canonical name "gem:sentry-raven"...
ℹ info [registry] › Adding extra data (checksums, download links) for available artifacts...
ℹ info [registry] › Pushing the changes...
ℹ info [registry] › Release registry updated
ℹ info
ℹ info Merging release branch: "release/3.0.2" into "master"...
ℹ info Merging: done.
ℹ info Removed the remote branch: "release/3.0.2"
✔ success Version 3.0.2 has been published!

@HazAT HazAT self-assigned this Aug 14, 2020
@HazAT HazAT marked this pull request as ready for review August 20, 2020 10:14
@HazAT HazAT requested a review from tonyo August 20, 2020 10:15
Copy link
Contributor

@tonyo tonyo left a comment

Choose a reason for hiding this comment

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

Nice!
Minor suggestions.
And CHANGELOG, please.

@HazAT HazAT merged commit c127791 into master Aug 20, 2020
@HazAT HazAT deleted the feat/gem-target branch August 20, 2020 11:20
BYK added a commit that referenced this pull request Mar 11, 2026
- simple-git: 3.30.0 → 3.33.0 (fixes CVE-2026-28292, CRITICAL CVSS 9.8)
  RCE via case-insensitive protocol.allow bypass in blockUnsafeOperationsPlugin
- tar: 7.5.10 → 7.5.11 (fixes CVE-2026-29786, HIGH CVSS 8.2)
  Hardlink path traversal via drive-relative linkpath

Also dismissed Dependabot alert #119 (@tootallnate/once, LOW severity)
as tolerable risk — blocked upstream by teeny-request pinning
http-proxy-agent@^5, and the vulnerability requires AbortSignal usage
patterns not present in Craft.
BYK added a commit that referenced this pull request Mar 11, 2026
)

## Security Dependency Updates

Addresses open Dependabot alerts by updating vulnerable direct
dependencies:

- **simple-git**: 3.30.0 → 3.33.0 — fixes
[CVE-2026-28292](GHSA-r275-fr43-pm7q)
(CRITICAL, CVSS 9.8). RCE via case-insensitive `protocol.allow` bypass
in `blockUnsafeOperationsPlugin`.
- **tar**: 7.5.10 → 7.5.11 — fixes
[CVE-2026-29786](GHSA-qffp-2rhf-9h96)
(HIGH, CVSS 8.2). Hardlink path traversal via drive-relative linkpath.

### Dismissed alert

[Alert #119](https://github.com/getsentry/craft/security/dependabot/119)
(`@tootallnate/once`, LOW severity) was dismissed as tolerable risk. The
fix requires a major version bump (v2 → v3) but is blocked upstream:
`teeny-request` pins `http-proxy-agent@^5` which hard-requires
`@tootallnate/once@2`. The vulnerability requires AbortSignal usage
patterns not present in Craft, and `@google-cloud/storage` is a
devDependency only.

### Verification

- ✅ Build passes
- ✅ All tests pass (6 pre-existing e2e failures due to missing EDITOR
env var — unrelated)
BYK added a commit that referenced this pull request Mar 16, 2026
- simple-git: 3.30.0 → 3.33.0 (fixes CVE-2026-28292, CRITICAL CVSS 9.8)
  RCE via case-insensitive protocol.allow bypass in blockUnsafeOperationsPlugin
- tar: 7.5.8 → 7.5.11 (fixes CVE-2026-29786, HIGH CVSS 8.2)
  Hardlink path traversal via drive-relative linkpath

Also dismissed Dependabot alert #119 (@tootallnate/once, LOW severity)
as tolerable risk — blocked upstream by teeny-request pinning
http-proxy-agent@^5, and the vulnerability requires AbortSignal usage
patterns not present in Craft.
BYK added a commit that referenced this pull request Mar 16, 2026
- simple-git: 3.30.0 → 3.33.0 (fixes CVE-2026-28292, CRITICAL CVSS 9.8)
  RCE via case-insensitive protocol.allow bypass in blockUnsafeOperationsPlugin
- tar: 7.5.8 → 7.5.11 (fixes CVE-2026-29786, HIGH CVSS 8.2)
  Hardlink path traversal via drive-relative linkpath

Also dismissed Dependabot alert #119 (@tootallnate/once, LOW severity)
as tolerable risk — blocked upstream by teeny-request pinning
http-proxy-agent@^5, and the vulnerability requires AbortSignal usage
patterns not present in Craft.
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.

2 participants