Please stop making semver breaking releases

[metatoaster]

This happened because the IsModule::CommonJS enum got added, it should have been a major version bump to prevent past versions of swc_compiler_base from picking this up. This happened because I was trying to build a tool that used this as a depdency.

This is not the first time someone complained about this, see #9481, though I am glad #5745 says this is being worked on.

error[E0004]: non-exhaustive patterns: `IsModule::CommonJS` not covered
  --> /home/build/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/swc_compiler_base-20.0.0/src/lib.rs:72:36
   |
72 |         let program_result = match is_module {
   |                                    ^^^^^^^^^ pattern `IsModule::CommonJS` not covered
   |
note: `IsModule` defined here
  --> /home/build/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/swc_config-3.1.1/src/is_module.rs:11:1
   |
11 | pub enum IsModule {
   | ^^^^^^^^^^^^^^^^^
...
14 |     CommonJS,
   |     -------- not covered
   = note: the matched value is of type `IsModule`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
   |
81 ~             IsModule::Unknown => parse_file_as_program(&fm, syntax, target, comments, &mut errors),
82 ~             IsModule::CommonJS => todo!(),
   |

For more information about this error, try `rustc --explain E0004`.
error: could not compile `swc_compiler_base` (lib) due to 1 previous error

[kdy1]

Sorry for the mistake. Not sure about the way to prevent this, though. Rust/cargo has no good tool for doing so.

[metatoaster]

Adding cargo-semver-checks to the existing GitHub actions CI workflow may be of some help.