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

Release 0.2.0 to main #91

Merged
merged 26 commits into from
Nov 5, 2024
Merged

Conversation

AntonReinhard
Copy link
Member

Adds some maintenance and improvements to CI scripts. Also updates the versions of QEDbase.jl, QEDcore.jl, QEDprocesses.jl, QEDfields.jl, and QEDevents.jl.

QEDbase.jl v0.3.0 release: https://github.com/QEDjl-project/QEDbase.jl/releases/tag/v0.3.0
QEDcore.jl v0.2.0 release: https://github.com/QEDjl-project/QEDcore.jl/releases/tag/v0.2.0
QEDprocesses.jl v0.3.0 release: https://github.com/QEDjl-project/QEDprocesses.jl/releases/tag/v0.3.0
QEDevents.jl v0.2.0 release: https://github.com/QEDjl-project/QEDevents.jl/releases/tag/v0.2.0
QEDfields.jl v0.2.0 release: https://github.com/QEDjl-project/QEDfields.jl/releases/tag/v0.2.0

Do not squash

SimeonEhrig and others added 26 commits September 13, 2024 10:44
As release PR, do not squash!
I set up the deploy keys and the private keys already.
I also changed the release template slightly to reflect that we no
longer have to tag or publish github releases ourselves.
~Open it as draft, because I want to test the package with the QED
ecosystem, before I release.~

fix QEDjl-project#27
- now, the script setups the dev branch versions of all QED projects in correct order to resolve circular dependencies
- handles also the compat entries, if the QED package to test has a new version

CI Integration tests: allow to modify the compat entries of dependencies
… entries) (QEDjl-project#74)

Now, the script setups the dev branch versions of all QED projects in
correct order to resolve circular dependencies
Handles also the compat entries, if the QED package to test has a new
version
…t section of other packages

If a QED package has increased its version, all other QED packages will continue to work in the CI tests, even if they have not yet updated their compat section.
…t section of other packages (QEDjl-project#79)

If a QED package has increased its version, all other QED packages will
continue to work in the CI tests, even if they have not yet updated
their compat section.

- [x] CI must pass: QEDjl-project/QEDcore.jl#77
Before, the function only returned dependencies, which was defined in required_dependencies. Now, the function also returns dependencies, which are (implicit) dependencies of the dependencies looking for.

Example: required_dependencies=["QEDfields"]
returned before: ["QEDfields"]
returns now: ["QEDbase", "QEDcore", "QEDfields"]
…core 0.2 and QEDbase 0.3 (QEDjl-project#83)

This pull request changes the compat entry for the `QEDcore` package
from `0.1` to `0.1, 0.2`.
This keeps the compat entries for earlier versions.



Note: I have not tested your package with this new compat entry.
It is your responsibility to make sure that your package tests pass
before you merge this pull request.
Changelog.md is no longer necessary, simplifying the release procedure
Changelog.md is no longer necessary, simplifying the release procedure
…name of the active package environment (QEDjl-project#88)

Here you find a PR which tests this fix:
QEDjl-project/QEDbase.jl#136
The final package updates for a new working state.
Has to wait until fields is registered.
@SimeonEhrig SimeonEhrig merged commit 33a40f5 into QEDjl-project:main Nov 5, 2024
5 checks passed
@AntonReinhard AntonReinhard deleted the release-0.2.0 branch November 5, 2024 14:27
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