Skip to content

Lint .js files - #291

Merged
rekmarks merged 2 commits into
developfrom
lint-js-files
Oct 26, 2020
Merged

rekmarks merged 2 commits into
developfrom
lint-js-files

Conversation

@rekmarks

@rekmarks rekmarks commented Oct 25, 2020 •

Copy link
Copy Markdown
Contributor

We weren't linting or formatting .js files. This PR ensures that we are.

@rekmarks
rekmarks requested a review from a team as a code owner October 25, 2020 18:10
@rekmarks rekmarks mentioned this pull request Oct 25, 2020

@whymarrh whymarrh left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@rekmarks
rekmarks merged commit 4523db5 into develop Oct 26, 2020
@rekmarks
rekmarks deleted the lint-js-files branch October 26, 2020 14:26
@rekmarks rekmarks mentioned this pull request Nov 3, 2020
Naz-Ovh pushed a commit to 0x-fork/metamask-core that referenced this pull request Sep 13, 2026
## Summary

- Updates `action-npm-publish` from v5 to v6
- Adds `id-token: write` permission to `publish-release` job in
`main.yml`
- Adds `permissions` block to `publish-npm` job in `publish-release.yml`
- Makes `NPM_TOKEN` secret optional

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Changes the production npm release path and auth model (OIDC +
optional token); misconfiguration could block publishes or affect
first-time package setup.
> 
> **Overview**
> Upgrades the release pipeline to **`MetaMask/action-npm-publish@v6`**
for both the dry-run and production npm publish jobs, matching v6’s
expected GitHub Actions setup.
> 
> **OIDC / permissions:** The reusable `publish-release` invocation in
`main.yml` now grants **`id-token: write`**, and the **`publish-npm`**
job sets explicit permissions (`contents: read`, `id-token: write`) so
the action can authenticate without relying only on a long-lived token
where OIDC is supported.
> 
> **Secrets contract:** `NPM_TOKEN` on the callable workflow is now
**optional** (`required: false`), and comments clarify it is only needed
for a **first-time** package publish; the dry-run step no longer
documents omitting `npm-token` explicitly. The real publish step still
passes `npm-token: ${{ secrets.NPM_TOKEN }}` when configured.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
9ae62d352b8c492e67e7fdfde8b23d71cf57306e. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants