fix: release-please config

[aladdin-add]

What is the purpose of this pull request?

fixes #181

What changes did you make? (Give an overview)

Update the configuration to align with eslint/css.

Related Issues

Is there anything you'd like reviewers to focus on?

The main difference is the revert of the commit: eslint/css@0d83c26

tested in the fork: aladdin-add#1

[aladdin-add]

removing the token - as it's not set in the org.

[Copilot]

Pull request overview

This PR aims to fix failing release-please automation (issue #181) by updating the GitHub Actions workflow and aligning the setup with eslint/css.

Changes:

• Reworked .github/workflows/release-please.yml to run release-please and publish to npm in a single job based on release_created.
• Removed the repository’s existing release-please config and manifest files under .github/release-please/.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

File	Description
.github/workflows/release-please.yml	Updates the release workflow steps/permissions and npm publish behavior.
.github/release-please/mainfest.json	Removes the release-please manifest file (note: filename suggests it may have been a misspelling of manifest).
.github/release-please/config.json	Removes the release-please configuration file.

Comments suppressed due to low confidence (2)

.github/release-please/config.json:1

• This file removal eliminates the repository’s release-please config, but no replacement default config (e.g., release-please-config.json at repo root) is added in this PR. Either restore this config (or add the default-named config file) so the workflow has a release strategy to apply.
  .github/release-please/mainfest.json:1
• This manifest file is removed, and there’s no .release-please-manifest.json (default location) added elsewhere in the PR. If the goal was to fix a filename mismatch (e.g., mainfest vs manifest), consider renaming/adding the correct manifest rather than deleting it so release-please can track released versions.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[nzakas]

Don't we also need a config file like in eslint/css?
https://github.com/eslint/css/blob/main/release-please-config.json

[aladdin-add]

Don't we also need a config file like in eslint/css? https://github.com/eslint/css/blob/main/release-please-config.json

the package was not published to jsr, so I just config it in:

eslint-plugin-security/.github/workflows/release-please.yml

Lines 19 to 21 in d5cb6a7

	with:
	release-type: node
	pull-request-title-pattern: "chore: release ${version} 🚀"

Does it make sense?

[aladdin-add]

added in 6c4a015.

[aladdin-add]

I'm merging it as it's blocking the new release.