[anuragxxd]

Description

Version bump for 2.0.0-alpha.49, made with node scripts/release.js set 2.0.0-alpha.49: the root, all released packages and package-lock.json. Only version lines change. @elixir-cloud/eslint-config moves from 0.0.1 to the shared version, as set up in #473.

Package changes since 2.0.0-alpha.48: #485 (overridable fetch() in the REST providers).

After merge: tag v2.0.0-alpha.49 on the merge commit (see "Releases" in CONTRIBUTING.md).

Verification

• node scripts/release.js check 2.0.0-alpha.49: passes.
• npm run lint (pre-commit hook, includes the build): passes.

Summary by Sourcery

Build:

• Update the root, released packages, ESLint configuration package, and lockfile to version 2.0.0-alpha.49.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This release-only PR updates the root project, all released packages, ESLint configuration package, and lockfile from 2.0.0-alpha.48 to 2.0.0-alpha.49 (including aligning the ESLint package with the shared version); no runtime code changes are included, and release verification is reported as passing.

File-Level Changes

Change	Details	Files
Synchronize the repository and released packages to version 2.0.0-alpha.49.	Bump the root project and seven released client/design packages from alpha.48. Promote the ESLint configuration package from 0.0.1 to the shared release version. Update corresponding package-lock metadata and dependency references.	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
Finalize the alpha.49 release metadata following the prior REST-provider fetch override changes.	Record the release as 2.0.0-alpha.49 without changing implementation code. Require tagging the merge commit as v2.0.0-alpha.49 after merge.	package.json package-lock.json

---

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!

Sourcery assessment

Needs a human reviewer. If these manifests are published, the packages will be identified by the new versions; reverting the source change cannot undo a published release, though the issue is bounded and can be corrected in a later release. If they are not published, reverting restores the previous versions.

---

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

• X
• Mastodon
• LinkedIn
• Facebook