puppeteer/release-please-config.json

{
  "last-release-sha": "2e3719cd7fbab551e99625bfb6198183aa23e7f5",
  "packages": {
    "packages/puppeteer": {
      "component": "puppeteer"
    },
    "packages/puppeteer-core": {
      "component": "puppeteer-core"
    },
    "packages/testserver": {},
    "packages/ng-schematics": {
      "initial-version": "0.1.0"
    }
  },
  "plugins": [
    {
      "type": "node-workspace",
      "merge": false
    },
    {
      "type": "linked-versions",
      "group-name": "puppeteer",
      "groupName": "puppeteer",
      "components": ["puppeteer", "puppeteer-core"]
    }
  ]
}
chore: bootstrap releases for path: . (#8416) 2022-05-30 10:02:43 +00:00			`{`
chore: bootstrap release-please (#9071) 2022-10-06 10:54:24 +00:00			`"last-release-sha": "2e3719cd7fbab551e99625bfb6198183aa23e7f5",`
chore: add component to release-please-config (#8428) 2022-05-30 13:38:08 +00:00			`"packages": {`
chore: update publish workflow (#9065) This PR combines the publishing workflows for npm packages and Docker. It also fixes an issue where multiple tags would trigger publishing all packages. 2022-10-06 09:44:52 +00:00			`"packages/puppeteer": {`
chore: define release-please component (#9252) 2022-11-11 10:43:11 +00:00			`"component": "puppeteer"`
			`},`
			`"packages/puppeteer-core": {`
			`"component": "puppeteer-core"`
chore: update publish workflow (#9065) This PR combines the publishing workflows for npm packages and Docker. It also fixes an issue where multiple tags would trigger publishing all packages. 2022-10-06 09:44:52 +00:00			`},`
feat(ng-schematics): Release @puppeteer/ng-schematics (#9244) What kind of change does this PR introduce? Adds `@puppeteer/ng-schematics` to the list of packages to be published to `npm` Did you add tests for your changes? Not relevant. If relevant, did you update the documentation? Not for in this PR. Summary We want to publish to `npm` so people can do `ng add @puppeteer/ng-schematics` and use it with Angular CLI. Does this PR introduce a breaking change? No Other information 2022-11-14 17:24:17 +00:00			`"packages/testserver": {},`
			`"packages/ng-schematics": {`
			`"initial-version": "0.1.0"`
			`}`
feat: separate puppeteer and puppeteer-core (#9023) This PR moves the puppeteer source code into separate mono-repo packages: - `puppeteer` and `puppeteer-core` are now separated into their own packages. - `puppeteer-core` has a new exports called `puppeteer-core/internal` for internal usage. Tests and various tools have been updated to accommodate the migration. 2022-10-05 12:17:03 +00:00			`},`
			`"plugins": [`
			`{`
chore: try linked versions for release (#9245) Let's give this plugin a try? with dependency pinning it seems useful to make sure these packages get released together. 2022-11-11 10:01:43 +00:00			`"type": "node-workspace",`
			`"merge": false`
			`},`
			`{`
			`"type": "linked-versions",`
			`"group-name": "puppeteer",`
chore: use groupName in release-please manifest (#9292) release-please does not handle `group-name` currently but very likely it will in the future. 2022-11-17 17:06:00 +00:00			`"groupName": "puppeteer",`
chore: try linked versions for release (#9245) Let's give this plugin a try? with dependency pinning it seems useful to make sure these packages get released together. 2022-11-11 10:01:43 +00:00			`"components": ["puppeteer", "puppeteer-core"]`
chore: add component to release-please-config (#8428) 2022-05-30 13:38:08 +00:00			`}`
feat: separate puppeteer and puppeteer-core (#9023) This PR moves the puppeteer source code into separate mono-repo packages: - `puppeteer` and `puppeteer-core` are now separated into their own packages. - `puppeteer-core` has a new exports called `puppeteer-core/internal` for internal usage. Tests and various tools have been updated to accommodate the migration. 2022-10-05 12:17:03 +00:00			`]`
chore: format release-please-configs (#8417) 2022-05-30 11:04:50 +00:00			`}`