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

Prepare release 0.4.0 #76

Closed
wants to merge 1 commit into from
Closed

Prepare release 0.4.0 #76

wants to merge 1 commit into from

Conversation

sosthene-nitrokey
Copy link
Collaborator

No description provided.

@robin-nitrokey
Copy link
Member

We have already released an upstream v0.4.0. Tagging a v0.4.0 on the fork too could be confusing. Why are we still using the fork anyway? We had already merged our contributions in trussed-dev#7. Would it be an option to merge the remaining changes and release an upstream v0.5.0?

@sosthene-nitrokey
Copy link
Collaborator Author

Looks like it. I think I kept using the fork because merging trussed-dev#7 was made through rebase and lead to diverging branches.

I'll fix that and start using upstream

@robin-nitrokey
Copy link
Member

Replaced by trussed-dev#14.

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