Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: snakemake/snakemake
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v9.11.7
Choose a base ref
...
head repository: snakemake/snakemake
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v9.11.8
Choose a head ref
  • 3 commits
  • 3 files changed
  • 3 contributors

Commits on Oct 2, 2025

  1. fix: use proper callable when accessing rule proxy with associated pa… 

    …th modifier (#3763)

### Description

<!--Add a description of your PR here-->

### QC
<!-- Make sure that you can tick the boxes below. -->

* [ ] The PR contains a test case for the changes or the changes are
already covered by an existing test case.
* [x] The documentation (`docs/`) is updated to reflect the changes or
this is not necessary (e.g. if the change does neither modify the
language nor the behavior or functionalities of Snakemake).


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Bug Fixes**
* Ensures path modifiers are correctly applied when callable inputs are
wrapped as file-like annotations, producing correct input paths.
* Preserves support for unwrapped callable inputs and aligns behavior
between wrapped and unwrapped callables.
* Reduces unexpected path mismatches in complex workflows, improving
input resolution reliability.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
    @johanneskoester
    johanneskoester authored Oct 2, 2025
    Configuration menu
    Copy the full SHA
    b5d12c8 View commit details
    Browse the repository at this point in the history

  2. docs: add snakemake logo to automatic mastodon release posts (#3764) 

    The mastodon release action has accidentally not been updated. So, no
logo image has been appended. This is now fixed upstream. Yet, the image
path does not to be indicated as the announcement post action crawls for
it (hopefully ;-) ).


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Chores**
* Improved release announcement automation for social posts by adjusting
how the logo image is referenced when publishing to Mastodon. This
increases reliability so the image consistently appears in release
announcements. No changes to application features or user workflows;
this is an infrastructure tweak to the publishing pipeline, with all
other settings and behavior remaining the same.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
    @cmeesters
    cmeesters authored Oct 2, 2025
    Configuration menu
    Copy the full SHA
    7b66250 View commit details
    Browse the repository at this point in the history

  3. chore(main): release 9.11.8 (#3766) 

    🤖 I have created a release *beep* *boop*
---


##
[9.11.8](v9.11.7...v9.11.8)
(2025-10-02)


### Bug Fixes

* use proper callable when accessing rule proxy with associated path
modifier ([#3763](#3763))
([b5d12c8](b5d12c8))


### Documentation

* add snakemake logo to automatic mastodon release posts
([#3764](#3764))
([7b66250](7b66250))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
    @snakemake-bot
    snakemake-bot authored Oct 2, 2025
    Configuration menu
    Copy the full SHA
    1549c8b View commit details
    Browse the repository at this point in the history
Loading