develop -> main merges do not trigger a release

Description

Merges from develop to main do not trigger a new build in Amplify. We are unsure of why this is happening because the project-stats workflow triggers a release of main without an issue.

• Review docs after investigating this issue and make any needed updates

Workaround: Wait for the project-stats workflow to run and trigger a release.

Possibly related things

The project-stats workflow commits directly to develop and cherry picks the commit to main. This is still working correctly, however it’s worth noting that the main branch is considered to be over 2000 commits ahead of main.

Acceptance Criteria

• Confirm with @jbeveland27 if there was a specific reason this approach was taken for project-stats
• Implement option 3

dont make project stats commits to develop. its those commits (and their frequency) that mainly contribute to this problem. it seems like we dont need to make them to develop since we make them to main anyways. if we went with this option, it kind of overlaps with solution 2 (and simplifies things), since we dont need to merge periodically, only when changes are introduced. additionally, there is another benefit we gain in that prs from develop -> main will be easier to review -- since there will be less changes in the PR.

[jbeveland27]

main is ahead of develop by design (for better or worse). It’s because the stats sync - commits are made to develop and then cherry-picked from develop to main, which creates a new commit in main that doesn’t exist in develop.

The important thing I tried to keep track of is when main is behind develop (which is easy to see in the GitHub UI), there are changes in stage that are pending release to production. Once main is no longer behind develop, you know staging and production are in sync.

[nr-opensource-bot]

🎉 This issue has been resolved in version 1.15.4 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀