Publish New Versions

[github-actions]

Version Updates

Merging this PR will release new versions of the following packages based on your change files.

javascriptcore-rs-sys

[2.0.0]

• 1e15afb (chore(deps): bump gir to latest and regenerate files #91) Bumped gir to ee0e85140a6f and regenerated bindings.
• df56e27 (chore(deps): update glib crates to 0.22 #88) Update glib crates to 0.22. Raised MSRV to 1.92.

javascriptcore-rs

[2.0.0]

• 1e15afb (chore(deps): bump gir to latest and regenerate files #91) Bumped gir to ee0e85140a6f and regenerated bindings.

• df56e27 (chore(deps): update glib crates to 0.22 #88) Update glib crates to 0.22. Raised MSRV to 1.92.

• 99e6915 (chore: update bitflags dependency version to 2.0 #86) Update bitflags dependency version to 2.0.

  This avoids duplicated dependencies in downstream crates.

[Legend-Master]

Waiting on #89

[Legend-Master]

@jbolda Does covector support this syntax? I could change this manually but still want to see if this can be supported directly.

[johncarmack1984]

(@jbolda hope it's okay I'm responding here) @Legend-Master I worked on some of covector's cargo workspace variant version bumping earlier this year. Short answer is 'Not yet, but it's a small gap.' covector only matches a dependency by its table key, so ffi = { package = "javascriptcore-rs-sys" } never matches and the requirement stays at 1.1.

PR to close the gap is up at jbolda/covector#438 as of a few minutes ago: it resolves the alias through package, in [dependencies], [target.*], and [workspace.dependencies].

Two things on this side either way. .changes/config.json would need "dependencies": ["javascriptcore-rs-sys"] on the javascriptcore-rs entry, or covector never looks at this line at all.

For this release, the manual edit to version = "2.0" is the way through. The improvements to covector that will enable this are a version bump away, meanwhile this PR puts the Tauri dep tree one step closer to a clean cargo audit for all those security conscious IT teams out there.