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.

Sign up for GitHub

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

Jump to bottom

chore(deps): upgrade gtk to 0.18 #801

Merged
merged 3 commits into from
Oct 16, 2023
Merged

chore(deps): upgrade gtk to 0.18 #801

merged 3 commits into from
Oct 16, 2023

Conversation

dklassic
Copy link
Contributor

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Docs
  • Code style update
  • Refactor
  • Build-related changes
  • Other, please describe:

Does this PR introduce a breaking change?

  • Yes
  • No

Checklist

  • This PR will resolve #___
  • A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
  • I have added a convincing reason for adding this feature, if necessary
  • It can be built on all targets and pass CI/CD.

Other information

@dklassic dklassic requested a review from a team as a code owner October 14, 2023 15:21
@dklassic
Copy link
Contributor Author

@amrbashir is there a need to wait for the clipboard removal to be published first before this can be merged? Or can we just merge them together?

@wusyong wusyong mentioned this pull request Oct 16, 2023
Merged
@amrbashir amrbashir changed the title Upgrade gtk to 0.18 chore(deps): upgrade gtk to 0.18 Oct 16, 2023
@amrbashir amrbashir merged commit 32ce759 into tauri-apps:dev Oct 16, 2023
9 checks passed
@dklassic dklassic deleted the gtk018 branch October 16, 2023 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@amrbashir amrbashir amrbashir approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@dklassic @amrbashir