Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Github doesn't correctly identify and push the tags for release to my repository #141

Open
elvapw opened this issue Sep 15, 2023 · 1 comment

Comments

@elvapw
Copy link

elvapw commented Sep 15, 2023

Issue Description:

I am encountering an issue with my Semantic Release configuration in a monorepo setup. The goal is to automate versioning and releases, but I'm facing an issue that prevents the release from working correctly. Here are the details:

When running Semantic Release (version 20.1.3) with my monorepo configuration, it doesn't correctly identify and tag the commits for release. The logs show the following information:
logs.txt

Configuration Files:

My .releaserc configuration is as follows:
releaserc.txt

Package.json File:
package.txt

Issue Details:

  • I'm using Semantic Release version 20.1.3.
  • The .releaserc configuration specifies that the release should occur on the master branch and uses various plugins.
  • The monorepo structure contains a package.json file in a child folder named childs/terraform-aws-ecr.

Problem Summary:

Semantic Release is not correctly identifying commits for release, even though it seems to recognize changes in the childs/terraform-aws-ecr folder. This is preventing the automated release process from working as expected.

Expected Outcome:

The expected outcome is for Semantic Release to correctly identify and tag commits for release based on the configuration provided.

Please let me know if you need any additional information or clarification on this issue. Thank you for your assistance.

@pmowrer
Copy link
Owner

pmowrer commented Jan 29, 2024

Thanks for the report @elvapw! It's difficult to debug this without more info. Are there commits missing on the log line semantic-release:get-commits Parsed commits:? How many were you expecting?

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

No branches or pull requests

2 participants