question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

publish not pushing changes to Github

See original GitHub issue

The problem

When running the publish command, changes occur correctly (updating versions + changelog), but nothing is uploaded to the repo… (excepted for the tag). In fact, no commit is even made (only pending changes). Therefore, the changelog remains empty and the version is not truly bumped… Am I missing a configuration?

Also, no errors, no branch protection, etc. Just a step that seems to be missing in the pipeline.

Expected behavior

All file changes are uploaded (as a new commit with chore: release?)

Additional context

config (toml):

[tool.semantic_release]
version_variable = ["modupipe/__init__.py:__version__"]
version_toml = ["pyproject.toml:tool.poetry.version"]
version_source = "tag"
branch = "master"
upload_to_pypi = false
upload_to_release = false
build_command = "poetry build"

action:

...
    steps:
      ...
      - name: Release
        env:
          GH_TOKEN: ${{ secrets.ACCESS_TOKEN }}  # has public_repo scope
          REPOSITORY_USERNAME: __token__
          REPOSITORY_PASSWORD: ${{ secrets.PYPI_TOKEN }}
        run: |
          git config --global user.name "Github Actions"
          git config --global user.email "actions@github.com"
          semantic-release publish --post

Issue Analytics

  • State:open
  • Created a year ago
  • Comments:7 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
vigenere23commented, Aug 23, 2022

The flasely True default for commit_version_number seems to indeed be the source of the problem. I’ve opened an issue for it. All the infos are correctly updated, which includes the changelog, the __init__.py version and the pyproject.toml version.

Unfortunately, I now have another bug where a commit stays pending on my local computer, even if the commit with the changelog and the version change has been pushed. But my branch is largely behind and the merge seems to have f**d things up, so I still need to test it correctly before confirming.

0reactions
github-actions[bot]commented, Nov 13, 2022

This bug report has been labelled as help wanted since there has been no activity in the last 3 weeks. It will not be closed.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Amplify Publish not pushing changes to cloud - won't update.
Today, everything was working fine - I'm 100% positive that I only made changes to the .vue files, but all of the sudden...
Read more >
Pushing changes to GitHub
As you commit changes to your project locally, you can push those changes to GitHub so that others may access them from the...
Read more >
Local Front end changes are not detected by publish #416
I have a react project deployed and is working as expected. Now I make some front end changes and issue "amplify publish". But...
Read more >
Amplify Publish Not Reflecting Changes · Issue #1465
I have Amplify Setup in my application which is working previously. Now Yesterday I made change and did amplify publish.
Read more >
Pushing commits to a remote repository
Use git push to push commits made on your local branch to a remote repository.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found