[uniqueg]

Summary

Version bump and curated notes for 2.0.0-alpha.51, as described in "Releases" in the contributing guide. It is the first release with @elixir-cloud/tes on the provider architecture (#443, #516): npm still has 1.0.1 as its latest, without providers, and apps need a provider that adds the user's access token to every TES request.

• node scripts/release.js set 2.0.0-alpha.51 sets the version of the root and of all 10 released packages (now including @elixir-cloud/tes, which chore(ecc-utils-ga4gh-tes): tes migration #516 made public), the matching entries in package-lock.json, and version and date-released (2026-11-14) in CITATION.cff.
• docs/releases/2.0.0-alpha.51.md: the curated notes, which the release workflow checks in prepare and publishes (first release since ci: align the release workflow #572 added this step).
• Contributing page: drops the statement that @elixir-cloud/tes is private and not released, and says to approve the staged versions dependencies first (design, then drs, trs, service-registry, then the rest), from Sourcery's review.

What #580 asks for:

• Outputs (fix(tes): send outputs from the create-run form #574): already on dev through chore(ecc-utils-ga4gh-tes): tes migration #516. run-create.ts builds request.outputs, and run-create.test.ts checks that a submitted form sends outputs. The notes list it under "Fixes".
• Token-adding provider in the TES docs: already on dev (docs/tes/providers.mdx, "Custom Providers", a RestTesProvider subclass that overrides fetch and sets Authorization on every request; plus the generic TokenWesProvider pattern in docs/providers.mdx).
• Scope change (build!: publish under the @elixir-on-cloud scope #522): not done yet, so this release stays under @elixir-cloud.

Light lane: version metadata, release notes and one sentence of the release docs; no code. I reviewed the diff myself.

Closes #580

How it was verified

• node scripts/release.js check 2.0.0-alpha.51: passes (exit 0).
• node scripts/release.js dist-tag 2.0.0-alpha.51: latest (2.0.0 prereleases stay on latest until 2.0.0).
• node scripts/release.js packages: 10 packages, including packages/ecc-client-ga4gh-tes.
• git diff of package-lock.json: only the 12 version lines.
• Curated notes: publish.py check docs/releases/2.0.0-alpha.51.md of elixir-cloud-aai/.github at the pinned commit of the workflow (31f22fc, v1.1.0): no findings (a file with a TODO and a bullet without references fails, as expected).
• node --test scripts/release.test.js scripts/utils.test.js: 27 of 27 pass.
• npm run lint (includes the build of all packages and the docs): 21 of 21 tasks pass.
• Local dry run of the npm job: node scripts/release.js pin 2.0.0-alpha.51 pins the 11 internal dependencies (reverted afterwards), the build passes, and npm pack --dry-run of @elixir-cloud/tes packs 2.0.0-alpha.51 with dist/providers/index.js (exports RestTesProvider), dist/react/index.js, custom-elements.json, README.md and LICENSE (67 files).
• CI: all checks pass (CI passed, Lint, PR title, Conflict markers, Test on Node 22 and 24, CodeQL, Read the Docs).
• Open code scanning alerts on dev: none.

Declined review findings

None. Sourcery's finding (approve the staged dependencies first) is about the approval on npm; the contributing guide now says so (804d673).

Open questions

None for this pull request. Steps before the tag are in the handover for the maintainer.

🤖 Generated with Claude Code

Summary by Sourcery

Release version 2.0.0-alpha.51 with the public provider-based TES package, service-registry and accessibility improvements, and curated release documentation.

New Features:

• Publish the first 2.0.0-alpha.51 release of @elixir-cloud/tes with provider-based authentication support and updated TES components.
• Add service-registry list filtering, pagination, row actions, and improved row selection behavior.
• Add accessibility labels to design package inputs and text areas.

Bug Fixes:

• Correct TES form submissions to send task outputs and improve WES styling and accessible success messaging.
• Restrict service-registry organization links to safe HTTP(S) URLs and address dependency and build-script security issues.

Enhancements:

• Align release documentation and package guidance with the public TES package and staged package approval order.

CI:

• Align pull request CI cancellation and Dependabot labeling with repository maintenance practices.

Documentation:

• Add curated 2.0.0-alpha.51 release notes covering TES providers, breaking changes, features, fixes, security updates, and maintenance work.
• Document TES components and providers and update preview endpoints and README citation information.

Chores:

• Bump the root and released package versions to 2.0.0-alpha.51 and update associated release metadata.

[sourcery-ai]

Reviewer's Guide

Configuration

Bump the root and released packages to 2.0.0-alpha.51, including TES now that it is public.

• CITATION.cff L54-55
• package.json L3
• packages/ecc-client-elixir-cloud-registry/package.json L5
• packages/ecc-client-elixir-drs-filer/package.json L5
• packages/ecc-client-elixir-trs-filer/package.json L5
• packages/ecc-client-ga4gh-drs/package.json L5
• packages/ecc-client-ga4gh-service-registry/package.json L5
• packages/ecc-client-ga4gh-tes/package.json L5
• packages/ecc-client-ga4gh-trs/package.json L5
• packages/ecc-client-ga4gh-wes/package.json L5
• packages/ecc-utils-design/package.json L5
• packages/eslint-config-elixir/package.json L3

Documentation

Read the curated release notes alongside the updated guidance on TES publication and staged-package approval order.

• apps/documentation/pages/docs/contributing.mdx L68, L143-148
• docs/releases/2.0.0-alpha.51.md L1-39

Lock files and vendored code

Check that the lockfile version metadata matches the release version bump.

• package-lock.json L3-37360 (12 small edits)

---

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.

[read-the-docs-community]

Documentation build overview

📚 cloud-components | 🛠️ Build #35896782 | 📁 Comparing 99a4b01 against latest (5961247)

  🔍 Preview build  

1 file changed

± docs/contributing/index.html

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.31%. Comparing base (5961247) to head (99a4b01).

Additional details and impacted files

@@           Coverage Diff           @@
##              dev     #582   +/-   ##
=======================================
  Coverage   75.31%   75.31%           
=======================================
  Files          37       37           
  Lines        9138     9138           
  Branches      470      470           
=======================================
  Hits         6882     6882           
  Misses       2245     2245           
  Partials       11       11           

☔ 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]

Linked issues

Checked at commit 99a4b01

#580 build: release @elixir-cloud/tes with providers · 3 of 4 met · 1 to check by hand

#	Requirement	Status	Notes
1	npm has a prerelease of TES that exports the REST provider and whose components accept a provider.	👀 Check by hand (external system)	After the release is published, verify that npm contains 2.0.0-alpha.51 with the provider export and provider-capable components.
2	Release notes name the breaking changes from 1.0.1.	✅ Met	The release notes list the element name, property name, and import-path changes.
3	Tasks created with the form contain outputs.	✅ Met	The form includes nonempty outputs in request.outputs, and its tests cover submitted outputs.
4	The TES docs show a token-adding provider.	✅ Met	The TES providers page shows a RestTesProvider subclass that adds a bearer token in fetch.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="packages/ecc-client-ga4gh-tes/package.json" line_range="5" />
<code_context>
 {
   "name": "elixir-cloud-components",
-  "version": "2.0.0-alpha.50",
+  "version": "2.0.0-alpha.51",
   "lockfileVersion": 3,
   "requires": true,
</code_context>
<issue_to_address>
**TES install fails during partial release**

When the maintainer approves `@elixir-cloud/tes@2.0.0-alpha.51` before `@elixir-cloud/design@2.0.0-alpha.51` is public, npm resolves `@elixir-cloud/tes`'s pinned runtime dependency `@elixir-cloud/design@2.0.0-alpha.51` and fails because that version is not public yet, so users cannot install TES. This also happens if approval stops after TES is published but before design is approved.

Require dependency-first approval and do not approve TES until its pinned internal dependencies are public.
</issue_to_address>

Sourcery assessment

Approval pending. 1 finding to address first.

Blocking findings: packages/ecc-client-ga4gh-tes/package.json:5

---

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

• X
• Mastodon
• LinkedIn
• Facebook

[sourcery-ai]

Sourcery assessment

Approved.

Sourcery withdrew this approval because the latest commits introduced blocking findings.