[uniqueg]

Summary

Version bump for 2.0.0-alpha.50, as described in "Releases" in the contributing guide: node scripts/release.js set 2.0.0-alpha.50 --date 2026-11-01 sets the version of the root and of all released packages, the matching entries in package-lock.json, and version and date-released in CITATION.cff.

Feather lane: only version metadata changes (12 files, one or two lines each; the lock file diff is the 11 version lines only).

Closes #544

How it was verified

• node scripts/release.js check 2.0.0-alpha.50: passes (exit 0).
• node scripts/release.js dist-tag 2.0.0-alpha.50: latest (2.0.0 prereleases stay on latest until 2.0.0).
• git diff of package-lock.json: only the 11 version lines.
• Local release dry run on this commit (Node 22): node --test scripts/release.test.js 25/25; node scripts/release.js pin 2.0.0-alpha.50 pins the 10 internal dependencies; npm run build and npm run lint pass (0 errors); npm pack --dry-run packs all 9 released packages at 2.0.0-alpha.50; none of them has 2.0.0-alpha.50 on npm yet.
• CI: all checks pass (CI passed, Lint, Test on Node 22 and 24, CodeQL, Sourcery, Codecov, Read the Docs).

🤖 Generated with Claude Code

Summary by Sourcery

Chores:

• Update the root project, released packages, lockfile, and citation metadata to version 2.0.0-alpha.50.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This release-only PR advances the root project and all published packages from 2.0.0-alpha.49 to 2.0.0-alpha.50, synchronizes the lockfile metadata, and records the new version and release date in the citation file; no functional code changes are included.

File-Level Changes

Change	Details	Files
Bump the repository and all published package versions to 2.0.0-alpha.50.	Update the root package manifest and eight published package manifests. Synchronize the corresponding package-lock.json version entries, limited to the expected 11 version lines.	package.json package-lock.json packages/ecc-client-elixir-cloud-registry/package.json packages/ecc-client-elixir-drs-filer/package.json packages/ecc-client-elixir-trs-filer/package.json packages/ecc-client-ga4gh-drs/package.json packages/ecc-client-ga4gh-service-registry/package.json packages/ecc-client-ga4gh-trs/package.json packages/ecc-client-ga4gh-wes/package.json packages/ecc-utils-design/package.json packages/eslint-config-elixir/package.json
Update citation metadata for the new prerelease.	Set the citation version to 2.0.0-alpha.50 and the release date to 2026-11-01.	CITATION.cff

Possibly linked issues

• Release 2.0.0-alpha.50 #544: The PR performs the issue’s requested version bump for the root, packages, lockfile, and citation metadata.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

Linked issues

#544 Release 2.0.0-alpha.50 · 2 of 4 met · 2 to check by hand

#	Requirement	Status	Notes
1	Set the root and released-package versions, package-lock.json versions, and CITATION.cff version and release date.	✅ Met	The root and all package manifests show 2.0.0-alpha.50; package-lock.json has 11 matching version entries, and CITATION.cff has version 2.0.0-alpha.50 and date-released 2026-11-01.
2	Merge the version-bump pull request into dev once CI has passed.	👀 Check by hand (external system)	Check the pull request and repository state to confirm CI passed and the change was merged into dev.
3	Have a maintainer tag the merge commit, approve the npm environment and staged versions, and fast-forward main.	👀 Check by hand (manual process)	Confirm a maintainer completed the tag, npm environment and staged-version approvals, and fast-forward to main.
4	Keep #509, #458, #535, #516, and #523 out of this release.	✅ Met	The change is limited to release metadata.

Sourcery assessment

Needs a human reviewer. If the release is published with the wrong version, consumers may install or depend on packages under an unintended version, and the published package metadata cannot be undone by reverting this commit. The impact is bounded and can be addressed with a corrected follow-up release.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 70.89%. Comparing base (c9db644) to head (29a168b).

Additional details and impacted files

@@           Coverage Diff           @@
##              dev     #545   +/-   ##
=======================================
  Coverage   70.89%   70.89%           
=======================================
  Files          23       23           
  Lines        5638     5638           
  Branches      190      190           
=======================================
  Hits         3997     3997           
  Misses       1636     1636           
  Partials        5        5           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[sourcery-ai]

Sourcery assessment

Approved.