releases cannot be marked as prereleases

[OdinValholl]

Recently, releases can no longer be created as prereleases by setting the "prerelease": true configuration in the release-please-config.json file.

Can this issue currently be confirmed?

My release-please-config.json looks like this:

{
  "pull-request-title-pattern": "Release(${component}) v${version}",
  "prerelease": true,
  "include-v-in-tag": true,
  "include-component-in-tag": true,
  "tag-separator": "-",
  "separate-pull-requests": true,
  "component-no-space": true,
  "packages": {
    ".": {
      "package-name": "any-app",
      "component": "any-app",
      "release-type": "simple"
    }
  }
}

In addition, with this scheme I couldn't find out exactly at which level the prerelease-type can be set because it doesn't quite agree with the documentation in the README.

As further information, when setting up my project I noticed that the autoreleases could not be created because the corresponding labels for the pull requests were missing in the GitHub repository. I had to create these manually so that the release pull requests were labeled correctly. Could this also be a current bug?

Thanks a lot!

[kallioaleksi]

I have the same issue, here's my config, it's slightly different:

{
  "packages": {
    ".": {
      "release-type": "node",
      "include-component-in-tag": false,
      "include-v-in-tag": true,
      "versioning": "prerelease",
      "prerelease": true,
      "prerelease-type": "beta",
      "changelog-path": "CHANGELOG.md",
      "bump-minor-pre-major": false,
      "bump-patch-for-minor-pre-major": false,
      "draft": false
    }
  },
  "$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json"
}

It creates the PR just fine, but doesn't mark it as a beta.

[OdinValholl]

What I've found so far is that your manifest.json shouldn't be an empty JSON.
It should at least contain something like { ".": "0.1.0-beta0" } or something like that

[kallioaleksi]

I noticed that as well, the issue is that the repo will have two different workflows, betas from main to env/dev and actual releases from main to env/prod.

My manifest is

{
  ".": "1.0.0"
}

and the actual releases work just fine (e.g. 1.1.0), but the prerelease workflow creates actual releases as well, not 1.1.0-beta and 1.1.0-beta2 etc).

[OdinValholl]

Yeah that's probably the only whay to trigger them seperately, or at least i couldn't find out yet how to do it in one workflow.

Do you seperate your manifest file for releases and prereleases?
And what happens if you set the config to "prerelease-type": "beta1" ?