`@electron-forge/cli@6.0.0-beta.25` installs sibling dependencies of latest tag `@6.0.0-beta.22` instead of the beta

• I have read the contribution documentation for this project.
• I agree to follow the code of conduct that this project follows, as appropriate.
• I have searched the issue tracker for an issue that matches the one I want to file, without success.

Using Yarn v1.7.0 I install 6.0.0-beta.25 @electron-forge/cli. Then initializing application.

$ yarn global add @electron-forge/cli@6.0.0-beta.25
$ electron-forge init project-name
√ Checking your system
√ Initializing Project Directory
√ Initializing Git Repository
√ Copying Starter Files
√ Initializing NPM Module
√ Installing NPM Dependencies

After all package.json has @electron-forge dependencies versioned after 6.0.0-beta.22:

{
  ...
  "devDependencies": {
    "@electron-forge/cli": "^6.0.0-beta.22",
    "@electron-forge/maker-deb": "^6.0.0-beta.22",
    "@electron-forge/maker-rpm": "^6.0.0-beta.22",
    "@electron-forge/maker-squirrel": "^6.0.0-beta.22",
    "@electron-forge/maker-zip": "^6.0.0-beta.22",
    "electron": "2.0.4"
  }
}

Not to say it’s pretty weird, but the beta package must utilize beta starter template, mustn’t it?

By the way, yeah, it’s only related to the beta stage (and it can still be an issue in future betas). Once v6 is released, I’ll be very happy to update my application. 😍

[MarshallOfSound]

I just don’t know the way to fetch it.

You can require the path to the core module’s package.json and read the version from it 👍

[MarshallOfSound]

This just requires a change to our init logic to install beta deps, if the initializer is a beta