getappmap / getappmap/appmap-python

CI: inconsistent release behavior

Open
#381 0 comments 0 reactions 1 assignee View on GitHub

@hleb-rubanau is already working on this.

Since Mar 5, 2026.

Dominant language
Python
Stars
104
Forks
17
PR merge metrics
No merged PRs in 30d

Description

When no release is produced because no release-triggering commits are present, publishing steps currently fails due to lack of artifacts generated. Instead, publishing must be explicitly skipped, ensuring status clarity.

Also, in the context of recent tooling changes, we need to ensure that publish pipeline still works end-to-end (this could be done for dev release, to avoid producing new official versions)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.