bump all packages versions

[panekj]

close #386
close #403
close #473
close #480

[panekj]

(didn't forget about this, just crunching at work so hard to keep things afloat you wouldn't believe)

[JounQin]

@panekj So this PR still doesn't receive updates after #403 (comment).

[panekj]

@panekj So this PR still doesn't receive updates after #403 (comment).

Comments in issues actually don't decrease work I have so no, there has been no update.

[panekj]

What is mainly missing is changelog to collect and write up.

[JounQin]

What is mainly missing is changelog to collect and write up.

@panekj They should be definitely managed by tools like changesets FYI, manually maintaining such verbose jobs is boring and tiring IMO.

[flying-sheep]

I personally like https://release-plz.ieni.dev/

It works like this:

1. create a changelog file in the supported format
2. add a workflow that runs the GitHub action
3. whenever you make commits, the action creates or updates a PR with the changelog
4. when you merge the PR, a new release is tagged and uploaded to crates.io

[JounQin]

@flying-sheep Where are the changelog contents from?

[flying-sheep]

there’s 3 paragraphs on the linked website, the second of which answers your question better than I can.

[JounQin]

Release-plz updates your changelogs with git-cliff using Keep a changelog format by default.

OK, it's still commit message based, what means the changelog can not be changed after committed. Not flexible as changesets.

[flying-sheep]

Whatever works best for you!

Just FYI: with release-plz, you can change the changelog in the PR before merging. The changelog/versions it autogenerates are not just message based, it also analyzes your code and figures out if your API changes classify as breaking or not.

But in the end, you are in control. Check out this example for a release PR: release-plz/release-plz#1170

PS: I’m just trying to help! I’d love a new Taplo release soon.

[JounQin]

# taplo/js/cli
yarn build

warning: unused import: `taplo_common::environment::Environment`
   --> src/lib.rs:216:9
    |
216 |     use taplo_common::environment::Environment;
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: `#[warn(unused_imports)]` on by default

warning: `taplo-wasm` (lib) generated 1 warning (run `cargo fix --lib -p taplo-wasm` to apply 1 suggestion)
    Finished dev [unoptimized] target(s) in 1.48s
Downloading wasm-bindgen version 0.2.82
[!] (plugin rpt2) Error: Could not load /Users/JounQin/Workspaces/GitHub/taplo/crates/taplo-wasm/Cargo.toml (imported by src/cli.ts): Rust compilation failed

It seems that I'm blocked by @wasm-tool/rollup-plugin-rust, does anyone has any idea?

cc @tamasfe @ia0 @panekj

Maybe we should migrate to https://github.com/napi-rs/napi-rs ASAP.

Resolved by upgrading wasm-bindgen crate.

@tamasfe @ia0 @panekj

Please help to review, so we can release the new versions.

[JounQin]

@tamasfe

Can we change the merge option from merge to squash or rebase (disable adding a new merge commit option)?

[JounQin]

I'll merge this PR as-is soon later.

[tamasfe]

@tamasfe

Can we change the merge option from merge to squash or rebase (disable adding a new merge commit option)?

Sure, squashing by default is a bad idea, but I prefer rebasing as well.

[JounQin]

@tamasfe Merging with a new commit can be disabled in GitHub settings.

[JounQin]

@tamasfe

https://crates.io/crates/taplo-cli

It seems the crates were not released correctly, can you help to release manually or give me the release permission so I can do it even after?

https://www.npmjs.com/package/@taplo/cli (v0.7.0 expected)

Same as js npm packages.

I'm JounQin on crates.io, and jounqin on npmjs.com.

[tamasfe]

Weird, the tags seem to be correct to me yet no CI started. I've sent invites both on crates and npm.

I'll figure out how to grant permission to the vscode extension at microsoft and openvsx later.

[JounQin]

@tamasfe Thanks for your trust, I've published all crates and npm packages successfully except https://crates.io/crates/lsp-async-stub, although it is not in emergency situation.

I'll keep working on better release workflow on #537 and #538.

[JounQin]

@tamasfe Would you mind to add me as owner for https://crates.io/crates/lsp-async-stub at the same time when you're free? So that I can help to publish a new version for it.