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.1.1 #55

Merged
merged 8 commits into from
Sep 3, 2024
Merged

Conversation

AntonReinhard
Copy link
Member

Release version 0.1.1 to main

This PR is opened from my fork. After discussion with @SimeonEhrig we have decided that we shouldn't need to keep the release-* branches since we have the tags to keep track of the previous versions. Since branches from this origin repository lead to race conditions in the gitlab mirroring, we should never push branches to this repository. The commits and common base of the dev and main branches are still preserved as long as we don't squash the release PRs.

SimeonEhrig and others added 8 commits July 15, 2024 09:24
Add changes from release branch 0.1.0 back to dev. 

don't forget: **no squishing**
Same changes as QEDjl-project#40, ported to dev.

Do not squish.
Rename the mul function to _mul since it is not exported.
Goes together with QEDjl-project/QEDbase.jl#110
See subtask in QEDjl-project#24 , it is actually unused currently anyways.
Fixes CI branch names and `deploydocs` call.
Apparently, the main branch did not ever deploy its documentation until
now and the dev branch didn't update anymore...
Copy link
Member

@szabo137 szabo137 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Understood. Hopefully in the future, those confusions will be resolved. For now, I am fine with releasing from forks, if there come from member accounts.

@AntonReinhard AntonReinhard merged commit 95641ea into QEDjl-project:main Sep 3, 2024
6 checks passed
@AntonReinhard AntonReinhard deleted the release-0.1.1 branch September 3, 2024 18:00
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.

3 participants