Skip to content

Release 1.2.0 - #34

Merged
almogtavor merged 2 commits into
mainfrom
release-1.2.0
Nov 16, 2026
Merged

almogtavor merged 2 commits into
mainfrom
release-1.2.0

Conversation

@Etelis

@Etelis Etelis commented Nov 16, 2026

Copy link
Copy Markdown
Member

Bumps the version to 1.2.0 for the release of #31 and #32: Lanes (one Buffer per lane, for DBO) and DispatchHandle exported from afdep. No native changes since 1.1.0.

Adds Lanes (several Buffers on one group, for DBO) and exports
DispatchHandle from afdep.

Signed-off-by: Itay Etelis <92247226+Etelis@users.noreply.github.com>
@Etelis
Etelis requested a review from almogtavor as a code owner November 16, 2026 07:36
@almogtavor
almogtavor merged commit c01f672 into main Nov 16, 2026
4 checks passed
@almogtavor
almogtavor deleted the release-1.2.0 branch November 16, 2026 12:24
Etelis added a commit that referenced this pull request Nov 16, 2026
## What and why

PR #34 set the version to 1.2.0, but nothing tagged or published it:
releases were created by hand, and v1.1.0 is still the latest one.

I added a workflow that runs when a merge to main changes
`pyproject.toml`. If `v<version>` has no release yet, it builds the
wheel and sdist, runs `tests/check_distribution.py`, checks that
`afdep.__version__` matches, tags the commit and creates the GitHub
release with both files attached. A version that is already released is
skipped, so ordinary merges do nothing.

Merging this PR will publish v1.2.0 from main, since it is still
missing. The notes are generated from the merged PRs and can be edited
afterwards.

The package is not on PyPI (`afdep-comm` does not exist there).
Publishing to PyPI needs an account decision, so I left it out.

## Checks

- [x] The workflow file parses; the build and distribution check are the
same commands CI already runs
- [ ] The first real run happens on merge
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

Successfully merging this pull request may close these issues.

2 participants