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

semantic-release publish is deleting files from dist/* directory #910

Closed
surya-sigtech opened this issue May 2, 2024 · 3 comments
Closed
Labels
bug Something isn't working properly

Comments

@surya-sigtech
Copy link

The problem

When running semantic-release publish in our CI workflow using Github Actions, the command is unexpectedly deleting files within the dist/ directory. It's worth noting that this directory is untracked and listed in our .gitignore file.

Expected behavior

We expect semantic-release publish to execute successfully without affecting any untracked files, simply pushing the new release.

Environment

  • We are using poetry as a build tool.
python --version
3.11.8
semantic-release --version
7.32.2
poetry --version
1.5.1

Configuration

[tool.semantic_release]
version_variable = [
    "{project_dir}/__version__.py:__version__",
    "pyproject.toml:version"
]
branch = "master"
changelog_components = "custom_changelog_generator.custom_changelog_generator"
upload_to_pypi = false
upload_to_release = false
commit_author= "xxx"
hcvs = "github"
build_command = "poetry build"

Logs

Only info logs are available.

Current version: 7.0.5, Current release version: 7.0.5
Bumping with a patch version to 7.0.6
Pushing new version
warning: Missing token: cannot post changelog to HVCS
Publish has finished

Additional Information:

The semantic-release command is executed in our Github Action step using the following command:

python -m poetry run semantic-release publish
@surya-sigtech surya-sigtech added the bug Something isn't working properly label May 2, 2024
@codejedi365
Copy link
Contributor

codejedi365 commented May 3, 2024

@surya-sigtech, are you able to upgrade to the latest version? If you can, it's highly likely the bug will not exist. I am less familiar with the v7 code as there was a heavy re-write for v8, and separately I do not plan to provide updates to v7.

The configuration has changed so you will need to update according to the migration instructions on the documentation site.

@codejedi365 codejedi365 added the awaiting-reply Waiting for response label May 3, 2024
Copy link

This issue has not received a response in 14 days. If no response is received in 7 days, it will be closed. We look forward to hearing from you.

@surya-sigtech
Copy link
Author

Not facing any issues after update
Thanks!! @codejedi365

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working properly
Projects
None yet
Development

No branches or pull requests

2 participants