Skip to content

chore: rename amplify-api-next refs to amplify-data#416

Merged
iartemiev merged 6 commits intomainfrom
rename-old-refs
Dec 18, 2024
Merged

chore: rename amplify-api-next refs to amplify-data#416
iartemiev merged 6 commits intomainfrom
rename-old-refs

Conversation

@iartemiev
Copy link
Member

@iartemiev iartemiev commented Dec 18, 2024

Changes

Find/replace amplify-api-next -> amplify-data throughout the codebase.

No code or functional changes. Only affects, comments, readme, JSON, GHA config, etc.

The majority of the changes are to explicit working_directory values in GHA. Running e2e suite to ensure the pipeline is intact.

Validation

Checklist

  • If this PR includes a functional change to the runtime or type-level behavior of the code, I have added or updated automated test coverage for this change. (see Testing Strategy README)
  • If this PR requires a docs update, I have linked to that docs PR above.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@iartemiev iartemiev requested review from a team as code owners December 18, 2024 16:22
@changeset-bot
Copy link

changeset-bot bot commented Dec 18, 2024

🦋 Changeset detected

Latest commit: e48025d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@iartemiev iartemiev enabled auto-merge (squash) December 18, 2024 16:53
@iartemiev iartemiev merged commit 8f8a6b6 into main Dec 18, 2024
9 checks passed
@iartemiev iartemiev deleted the rename-old-refs branch January 16, 2025 12:23
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

Comments