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.
...
- 3 commits
- 13 files changed
- 3 contributors
Commits on Oct 14, 2024
-
docs: update installation docs to reflect changes in conda ecosystem (#…
…3141) <!--Add a description of your PR here--> ### QC <!-- Make sure that you can tick the boxes below. --> * [x] 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).
-
feat: more robust parameter and code change detection and transparent…
… reporting of detected changes (#3140) <!--Add a description of your PR here--> ### QC <!-- Make sure that you can tick the boxes below. --> * [x] 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 - **New Features** - Enhanced tracking of job parameters within the Snakemake framework. - Introduced a new `ParamsChange` dataclass for improved clarity in parameter change tracking. - Added logging functions to track jobs with outdated or missing metadata. - Implemented automatic updates of Conda in the CI workflow. - **Improvements** - Simplified logic for job execution reasons, improving readability and maintainability. - Updated job parameter change reporting for more detailed insights during execution. - Enhanced visibility of job metadata status during workflow execution for better debugging. - Introduced new tests to validate parameter handling and metadata management. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
-
chore(main): release 8.23.0 (#3142)
🤖 I have created a release *beep* *boop* --- ## [8.23.0](v8.22.0...v8.23.0) (2024-10-14) ### Features * More robust parameter and code change detection and transparent reporting of detected changes ([#3140](#3140)). For setups using remote storage, this will lead to missing metadata records because the key used for storing the metadata is now the remote storage query instead of the path to the local copy. The reason is that the latter can be user-specific and therefore previously could have let led to e.g. different rerun behavior for different users. ### Documentation * update installation docs to reflect changes in conda ecosystem ([#3141](#3141)) ([e83b8aa](e83b8aa)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Johannes Köster <[email protected]>
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v8.22.0...v8.23.0