Skip to content

chore: Resolve merge conflicts for 2026.07.2 - #2244

Merged
divbzero merged 7 commits into
developfrom
release/2026.07.2
Jul 22, 2026
Merged

chore: Resolve merge conflicts for 2026.07.2#2244
divbzero merged 7 commits into
developfrom
release/2026.07.2

Conversation

@divbzero

@divbzero divbzero commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

This resolves merge conflicts in #2243 in preparation for release 2026.07.2. The merge conflicts arose from our use of a release/2026.07.1 branch for release 2026.07.1.

aweiland and others added 7 commits June 17, 2026 15:54
* fix: let AssignmentsTable resolve and report picked participants

* fix: remember search-selected participants in ActivityAssignDrawer
* feat(M2-10875): update footer links from mindlogger.org to gettingcurious.com

* feat(M2-10875): update hardcoded terms link in SignUpForm to gettingcurious.com

* feat(M2-10875): update README link from mindlogger.org to gettingcurious.com

* fix: use www.gettingcurious.com instead of apex domain
* chore: bump axios, vitest, react-router-dom, lodash-es to patched versions to resolve Dependabot alerts

* fix: prevent false Save Changes prompt

* fix: deep-scan dirtyFields to avoid false Save Changes prompt after undo

* fix: use hasFormChanges instead of isDirty in sendRequestWithPasswordCheck

* fix: tests
@aws-amplify-us-east-1

Copy link
Copy Markdown

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-2244.d2ccder08v9rmu.amplifyapp.com

@adeiji
adeiji self-requested a review July 21, 2026 23:49

@adeiji adeiji left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Took a look at the merge commit and it looks good

@divbzero
divbzero merged commit d408589 into develop Jul 22, 2026
6 checks passed
@divbzero

Copy link
Copy Markdown
Contributor Author

The squash commit from this PR did not allow GitHub to resolve merge conflicts in #2243. I ended up merging release/2026.07.1 to develop manually with a merge commit.

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.

4 participants