-
Notifications
You must be signed in to change notification settings - Fork 5
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.1.6 #56
Merged
Merged
Release 0.1.6 #56
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Release v0.1.4 See merge request QEDjl/QEDbase.jl!21
Enhancement for the gitlab-ci See merge request QEDjl/QEDbase.jl!16
Corrected Gamma matrices and add test for correct matrix definition Closes #21 See merge request QEDjl/QEDbase.jl!22
fixed AdjointBiSpinor multiplication Closes #22 See merge request QEDjl/QEDbase.jl!23
I updated the gitignore to keep all items that are already ignored in addition to adding the following search parameters in https://www.gitignore.io: - julia - windows - macos - linux - vs - git - vim - emacs You can see a hyperlink with my search parameters [here](https://www.toptal.com/developers/gitignore?templates=julia,windows,macos,linux,vs,git,vim,emacs) This pull request fixes issue #6
Integration tests checks if all QED sub packages are still working with the code changes in a PR, if they use the sub package, where the PR is open. This [test PR](#3) demonstrate, how it works. - This [commit](e9c2f31) introduces an API break. Therefore the [integration test job](https://gitlab.com/hzdr/qedjl-project/QEDbase-jl/-/jobs/4964972487) fails. - The following up [commit](fd3d781) points to a feature branch in the commit message, which solves the API break for the using sub package. Therefore the [test passes](https://gitlab.com/hzdr/qedjl-project/QEDbase-jl/-/jobs/4965235928). For more details, check the [documentation](https://github.com/QEDjl-project/QED.jl/blob/dev/docs/src/ci.md#integration-tests-for-ci-users).
Before the format_all.jl script needs to be execute from the project root directory. Now the script can be executed from every directory path.
In an offline discussion, we decided to remove the `Manifest.toml`s from the library, since a library should build its dependencies from scratch every time.
Resolves #21. ## Applied changes * Removed `sorting` argument from `CitationsBibliography` * Adjusted syntax of the latest version of `makedocs` using the `plugin` keyword * Fixed typo in docstrings * Removed docstring of the `QEDbase` module (this feature might be broken) * Added `QEDbase` as a dependency to docs --------- Co-authored-by: Uwe Hernandez Acosta <[email protected]>
Co-authored-by: Anton Reinhard <[email protected]> Co-authored-by: AntonReinhard <[email protected]> Co-authored-by: Uwe Hernandez Acosta <[email protected]> Co-authored-by: Tom Jungnickel <[email protected]>
- tests also the latest unreleased version 1.10 (can fail) - integration tests still testing a single version. Will be extended in another PR.
Add Compat Helper CI job Generated a ssh key pair for the deployment and add it to the repository like described in the [compat helper documentation](https://juliaregistries.github.io/CompatHelper.jl/stable/#Creating-SSH-Key). The job cannot be triggered, until it was merged in dev. We had already the problem in #28 . This PR is a copy of: QEDjl-project/QEDprocesses.jl#27
…ing compat) (#40) This pull request changes the compat entry for the `DocStringExtensions` package from `0.8.5` to `0.8.5, 0.9`. 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. Co-authored-by: CompatHelper Julia <[email protected]>
Fix base_state for AllPol and AllSpin Provide a way to consistently get an SVector from the return value of base_state --------- Co-authored-by: Rubydragon <[email protected]>
Adding the changes from releasing 0.1.5 --------- Co-authored-by: Uwe Hernandez Acosta <[email protected]>
This if-condition avoids, that the compat helper is executed in forks. copy of: QEDjl-project/QEDfields.jl#19
This fix is necessary for julia 1.10 Co-authored-by: Rubydragon <[email protected]>
This PR improves the coverage for coordinates tested in `test/particle.jl` to the full domains for angles in spherical coordinates for photons. ### Summary - added safetestsets to modulize the unit tests - added more cases for the angles in spherical coordinates - added a fix for #49 This resolves #49 --------- Co-authored-by: Uwe Hernandez Acosta <[email protected]>
@SimeonEhrig Do you have an idea, why the GitLab pipeline is not triggered? Edit: Nevermind, it just took some time for the bot to trigger. |
Unfortunately, that happens. |
SimeonEhrig
approved these changes
Jan 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With this release, the latest changes from
dev
are merged intomain
. Caused by issues with the git history, the changes seen in this PR also include commits since release 0.1.4.Lesson learned
After merging the release branch into
main
, the former should not been touched till it's merged intodev
.