chore(main): release 1.0.0

[github-actions]

🤖 I have created a release beep boop

1.0.0 (2022-07-11)

Features

• bring in new changes from ZISI (aaa06bf)
• extract implementation from ZISI (0922b9e)
• make helper module configurable (212bd30)
• make helperModule a predicate (32559c7)

Bug Fixes

• deps: update babel monorepo to v7.18.8 (56255e4)
• point entrypoint to index.js (b52dacf)

---

This PR was generated with Release Please. See documentation.

[Skn0tt]

@danez I extracted out the in-source-configuration part of ZISI into this repository, so we can reuse it in edge-bundler. Could you give main a review? (using this PR as a stand-in)

[danez]

• CODEOWNERS <- @netlify/runtime-pod-compute ?
• newer fossa workflow (v3) from here: https://github.com/netlify/zip-it-and-ship-it/blob/main/.github/workflows/fossa.yml
• pr labeler workflow: v1.0.0 -> v1
• Do we use stalebot?
• The copied code is not from the latest version of zisi!

[Skn0tt]

oh, maybe I forgot to pull before copying 😅 Thx, good that you caught this! I'll ping here again once I updated

[Skn0tt]

Updated Codeowners/Fossa/labeler in 46d180c...0f23188

Stalebot was added by #2, so I guess we use it now 🤷

[Skn0tt]

Brought in ZISI changes in aaa06bf :)

[danez]

The release-please job should use the token-generator, otherwise the workflows will not be triggered in PRs (like this one).
https://github.com/netlify/binary-info/blob/main/.github/workflows/release-please.yml#L10-L20

Also the release will not work:

• NPM_TOKEN secret is not set yet, the same is true for the token generator secrets.
• npm publish needs --access public otherwise it will try to create a private package initially, similar to : https://github.com/netlify/binary-info/blob/main/.github/workflows/release-please.yml#L33

Otherwise LGTM.

[danez]

And https://github.com/netlify/in-source-config/blob/main/package.json#L3 should probably be lifted before release :)

[Skn0tt]

The release-please job should use the token-generator

Can you elaborate on that? I use release-please v3 in Skn0tt/datapact#157, and it works fine without token-generator.

NPM_TOKEN secret is not set yet, the same is true for the token generator secrets.

Asked in Slack for some admin to change that.

npm publish needs --access public

good point! done in 72c02f5

private: true needs to be lifted

done in 72c02f5

[danez]

Can you elaborate on that? I use release-please v3 in Skn0tt/datapact#157, and it works fine without token-generator.

Also in the linked PR it is not running the tests etc. This is because a workflow (in our cases release-please) cannot trigger other workflows through PRs, because otherwise, it could endup in an endless loop of triggering workflows. https://docs.github.com/en/actions/using-workflows/triggering-a-workflow#triggering-a-workflow-from-a-workflow
But if we use our own token like in the other repos it does work, because it is not github action triggering the workflow but the Github APP associated with the token.

In theory this is okay, because the release PR does not change anything so no need for tests and other stuff, but if we have required checks that need to be run like in your linked PR you won't be able to merge it ever.

[Skn0tt]

Today I learned! That makes total sense. I'll update it.

[danez]

In my private repos I used a custom github token. https://github.com/reactjs/react-docgen/blob/main/.github/workflows/release-please.yml#L17
Only funny thing is then that the PRs are made in my name: reactjs/react-docgen#635 :)