* chore(deps): bump github.com/auth0/go-auth0/v2 from 2.13.0 to 2.14.0 (#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] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Chore: Updated CI workflows to trigger releases based on branches (#1565)

* Updated goreleaser condition for main and beta branches

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

* wf update

* chore: Add Sentry DSN so crash reporting works in all builds (#1564)

* 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.

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Kunal Dawar <[email protected]>

…Variations (Beta) (#1562)

* feat: Add support for Experiements, Feature-Flags, Segments and Variations (Beta)

* Added docs and lint

* Lint

* docs update

* Updated integration tests

* lint

* Updated integration test

* Updated exp

* Minor updates

* Updated docs

* feat: add status command for experiments and feature flags

* feat: enhance segment rules and validation in CLI

* refactor: remove debug option and simplify segment rules parsing

---------

Co-authored-by: ramya18101 <[email protected]>

…ta versions (#1570)

* chore: Update README, CONTRIBUTING GUIDE and install.sh script for beta versions

* fix: correct beta release detection in install.sh and document beta package manager installs

---------

Co-authored-by: Kunal Dawar <[email protected]>
Co-authored-by: Ramya Anusri <[email protected]>

Move experiments, feature-flags, and segments under a single `auth0 experimentation` parent command, mirroring the Management API's experimentation grouping. Variations remain nested under feature-flags.

Also improves the experiment allocation flow: interactive variation multi-select (choose 1 to 20) with paging; enforce the 20-allocation maximum and weight bounds on the non-interactive --allocations flag; diff-based updates that send only changed fields (allocations replaced wholesale when edited); interactive update opens editors for feature-flag parameters, variation overrides, and segment rules pre-filled with current values; render the full API response on update output.

Regenerates docs and updates integration tests and helper scripts.