Skip to content

test: New CI changes while merging to beta#1569

Closed
duedares-rvj wants to merge 5 commits into
betafrom
tempBeta
Closed

test: New CI changes while merging to beta#1569
duedares-rvj wants to merge 5 commits into
betafrom
tempBeta

Conversation

@duedares-rvj

Copy link
Copy Markdown
Member

This is a test branch that shall not be merged.

dependabot Bot and others added 5 commits June 26, 2026 13:37
…1563)

Bumps [github.com/auth0/go-auth0/v2](https://github.com/auth0/go-auth0) from 2.13.0 to 2.14.0.
- [Release notes](https://github.com/auth0/go-auth0/releases)
- [Changelog](https://github.com/auth0/go-auth0/blob/main/CHANGELOG.md)
- [Commits](auth0/go-auth0@v2.13.0...v2.14.0)

---
updated-dependencies:
- dependency-name: github.com/auth0/go-auth0/v2
  dependency-version: 2.14.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
)

* Updated goreleaser condition for main and beta branches

* Chore: Updated CI for main branch and Added CI for Beta

* wf update
* Hardcode Sentry DSN so crash reporting works in all builds

The Sentry DSN was injected at build time via ldflags from a SENTRY_DSN
secret. That value has been empty in released binaries since around v1.10,
so crash reporting has effectively been disabled, and it cannot work at all
for from-source builds such as Homebrew Core.

A Sentry DSN is a public, write-only key that is safe to ship inside client
binaries, so this hardcodes it as the default. The build-time injection is
removed from the release pipeline so every build path (releases, Homebrew
Core, and plain go build) reports to Sentry consistently.

* Skip Sentry reporting for local/dev builds

Reporting now keys off buildinfo.Version instead of the Sentry DSN.
Local builds stamp the version as "dev" (and a plain go build leaves
it empty), so ReportException returns early for those and panics
re-panic with a real stack trace. Release and Homebrew Core builds
carry a real version and continue to report.
@duedares-rvj duedares-rvj requested a review from a team as a code owner June 28, 2026 14:09
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