9577d5145afbd269158da3e8dcbcffe210a70c42
21 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
dependabot[bot]
|
9577d5145a |
build(deps-dev): bump the development-dependencies group with 3 updates (#69)
Bumps the development-dependencies group with 3 updates: [esbuild](https://github.com/evanw/esbuild), [undici](https://github.com/nodejs/undici) and [yaml](https://github.com/eemeli/yaml). Updates `esbuild` from 0.19.4 to 0.19.5 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/evanw/esbuild/releases">esbuild's releases</a>.</em></p> <blockquote> <h2>v0.19.5</h2> <ul> <li> <p>Fix a regression in 0.19.0 regarding <code>paths</code> in <code>tsconfig.json</code> (<a href="https://redirect.github.com/evanw/esbuild/issues/3354">#3354</a>)</p> <p>The fix in esbuild version 0.19.0 to process <code>tsconfig.json</code> aliases before the <code>--packages=external</code> setting unintentionally broke an edge case in esbuild's handling of certain <code>tsconfig.json</code> aliases where there are multiple files with the same name in different directories. This release adjusts esbuild's behavior for this edge case so that it passes while still processing aliases before <code>--packages=external</code>. Please read the linked issue for more details.</p> </li> <li> <p>Fix a CSS <code>font</code> property minification bug (<a href="https://redirect.github.com/evanw/esbuild/issues/3452">#3452</a>)</p> <p>This release fixes a bug where esbuild's CSS minifier didn't insert a space between the font size and the font family in the <code>font</code> CSS shorthand property in the edge case where the original source code didn't already have a space and the leading string token was shortened to an identifier:</p> <pre lang="css"><code>/* Original code */ .foo { font: 16px"Menlo"; } <p>/* Old output (with --minify) */ .foo{font:16pxMenlo}</p> <p>/* New output (with --minify) */ .foo{font:16px Menlo} </code></pre></p> </li> <li> <p>Fix bundling CSS with asset names containing spaces (<a href="https://redirect.github.com/evanw/esbuild/issues/3410">#3410</a>)</p> <p>Assets referenced via CSS <code>url()</code> tokens may cause esbuild to generate invalid output when bundling if the file name contains spaces (e.g. <code>url(image 2.png)</code>). With this release, esbuild will now quote all bundled asset references in <code>url()</code> tokens to avoid this problem. This only affects assets loaded using the <code>file</code> and <code>copy</code> loaders.</p> </li> <li> <p>Fix invalid CSS <code>url()</code> tokens in <code>@import</code> rules (<a href="https://redirect.github.com/evanw/esbuild/issues/3426">#3426</a>)</p> <p>In the future, CSS <code>url()</code> tokens may contain additional stuff after the URL. This is irrelevant today as no CSS specification does this. But esbuild previously had a bug where using these tokens in an <code>@import</code> rule resulted in malformed output. This bug has been fixed.</p> </li> <li> <p>Fix <code>browser</code> + <code>false</code> + <code>type: module</code> in <code>package.json</code> (<a href="https://redirect.github.com/evanw/esbuild/issues/3367">#3367</a>)</p> <p>The <code>browser</code> field in <code>package.json</code> allows you to map a file to <code>false</code> to have it be treated as an empty file when bundling for the browser. However, if <code>package.json</code> contains <code>"type": "module"</code> then all <code>.js</code> files will be considered ESM, not CommonJS. Importing a named import from an empty CommonJS file gives you undefined, but importing a named export from an empty ESM file is a build error. This release changes esbuild's interpretation of these files mapped to <code>false</code> in this situation from ESM to CommonJS to avoid generating build errors for named imports.</p> </li> <li> <p>Fix a bug in top-level await error reporting (<a href="https://redirect.github.com/evanw/esbuild/issues/3400">#3400</a>)</p> <p>Using <code>require()</code> on a file that contains <a href="https://v8.dev/features/top-level-await">top-level await</a> is not allowed because <code>require()</code> must return synchronously and top-level await makes that impossible. You will get a build error if you try to bundle code that does this with esbuild. This release fixes a bug in esbuild's error reporting code for complex cases of this situation involving multiple levels of imports to get to the module containing the top-level await.</p> </li> <li> <p>Update to Unicode 15.1.0</p> <p>The character tables that determine which characters form valid JavaScript identifiers have been updated from Unicode version 15.0.0 to the newly-released Unicode version 15.1.0. I'm not putting an example in the release notes because all of the new characters will likely just show up as little squares since fonts haven't been updated yet. But you can read <a href="https://www.unicode.org/versions/Unicode15.1.0/#Summary">https://www.unicode.org/versions/Unicode15.1.0/#Summary</a> for more information about the changes.</p> <p>This upgrade was contributed by <a href="https://github.com/JLHwung"><code>@JLHwung</code></a>.</p> </li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/evanw/esbuild/blob/main/CHANGELOG.md">esbuild's changelog</a>.</em></p> <blockquote> <h2>0.19.5</h2> <ul> <li> <p>Fix a regression in 0.19.0 regarding <code>paths</code> in <code>tsconfig.json</code> (<a href="https://redirect.github.com/evanw/esbuild/issues/3354">#3354</a>)</p> <p>The fix in esbuild version 0.19.0 to process <code>tsconfig.json</code> aliases before the <code>--packages=external</code> setting unintentionally broke an edge case in esbuild's handling of certain <code>tsconfig.json</code> aliases where there are multiple files with the same name in different directories. This release adjusts esbuild's behavior for this edge case so that it passes while still processing aliases before <code>--packages=external</code>. Please read the linked issue for more details.</p> </li> <li> <p>Fix a CSS <code>font</code> property minification bug (<a href="https://redirect.github.com/evanw/esbuild/issues/3452">#3452</a>)</p> <p>This release fixes a bug where esbuild's CSS minifier didn't insert a space between the font size and the font family in the <code>font</code> CSS shorthand property in the edge case where the original source code didn't already have a space and the leading string token was shortened to an identifier:</p> <pre lang="css"><code>/* Original code */ .foo { font: 16px"Menlo"; } <p>/* Old output (with --minify) */ .foo{font:16pxMenlo}</p> <p>/* New output (with --minify) */ .foo{font:16px Menlo} </code></pre></p> </li> <li> <p>Fix bundling CSS with asset names containing spaces (<a href="https://redirect.github.com/evanw/esbuild/issues/3410">#3410</a>)</p> <p>Assets referenced via CSS <code>url()</code> tokens may cause esbuild to generate invalid output when bundling if the file name contains spaces (e.g. <code>url(image 2.png)</code>). With this release, esbuild will now quote all bundled asset references in <code>url()</code> tokens to avoid this problem. This only affects assets loaded using the <code>file</code> and <code>copy</code> loaders.</p> </li> <li> <p>Fix invalid CSS <code>url()</code> tokens in <code>@import</code> rules (<a href="https://redirect.github.com/evanw/esbuild/issues/3426">#3426</a>)</p> <p>In the future, CSS <code>url()</code> tokens may contain additional stuff after the URL. This is irrelevant today as no CSS specification does this. But esbuild previously had a bug where using these tokens in an <code>@import</code> rule resulted in malformed output. This bug has been fixed.</p> </li> <li> <p>Fix <code>browser</code> + <code>false</code> + <code>type: module</code> in <code>package.json</code> (<a href="https://redirect.github.com/evanw/esbuild/issues/3367">#3367</a>)</p> <p>The <code>browser</code> field in <code>package.json</code> allows you to map a file to <code>false</code> to have it be treated as an empty file when bundling for the browser. However, if <code>package.json</code> contains <code>"type": "module"</code> then all <code>.js</code> files will be considered ESM, not CommonJS. Importing a named import from an empty CommonJS file gives you undefined, but importing a named export from an empty ESM file is a build error. This release changes esbuild's interpretation of these files mapped to <code>false</code> in this situation from ESM to CommonJS to avoid generating build errors for named imports.</p> </li> <li> <p>Fix a bug in top-level await error reporting (<a href="https://redirect.github.com/evanw/esbuild/issues/3400">#3400</a>)</p> <p>Using <code>require()</code> on a file that contains <a href="https://v8.dev/features/top-level-await">top-level await</a> is not allowed because <code>require()</code> must return synchronously and top-level await makes that impossible. You will get a build error if you try to bundle code that does this with esbuild. This release fixes a bug in esbuild's error reporting code for complex cases of this situation involving multiple levels of imports to get to the module containing the top-level await.</p> </li> <li> <p>Update to Unicode 15.1.0</p> <p>The character tables that determine which characters form valid JavaScript identifiers have been updated from Unicode version 15.0.0 to the newly-released Unicode version 15.1.0. I'm not putting an example in the release notes because all of the new characters will likely just show up as little squares since fonts haven't been updated yet. But you can read <a href="https://www.unicode.org/versions/Unicode15.1.0/#Summary">https://www.unicode.org/versions/Unicode15.1.0/#Summary</a> for more information about the changes.</p> <p>This upgrade was contributed by <a href="https://github.com/JLHwung"><code>@JLHwung</code></a>.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
dependabot[bot]
|
3bb715c53d |
build(deps-dev): bump undici from 5.25.4 to 5.26.2 (#65)
Bumps [undici](https://github.com/nodejs/undici) from 5.25.4 to 5.26.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/nodejs/undici/releases">undici's releases</a>.</em></p> <blockquote> <h2>v5.26.2</h2> <p>Security Release, CVE-2023-45143.</p> <h2>v5.26.1</h2> <h2>What's Changed</h2> <ul> <li>Fix publish undici-types once and for all! by <a href="https://github.com/Ethan-Arrowood"><code>@Ethan-Arrowood</code></a> in <a href="https://redirect.github.com/nodejs/undici/pull/2338">nodejs/undici#2338</a></li> <li>Fix node detection omfg by <a href="https://github.com/KhafraDev"><code>@KhafraDev</code></a> in <a href="https://redirect.github.com/nodejs/undici/pull/2341">nodejs/undici#2341</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/nodejs/undici/compare/v5.26.0...v5.26.1">https://github.com/nodejs/undici/compare/v5.26.0...v5.26.1</a></p> <h2>v5.26.0</h2> <h2>What's Changed</h2> <ul> <li>use npm install instead of npm ci by <a href="https://github.com/Ethan-Arrowood"><code>@Ethan-Arrowood</code></a> in <a href="https://redirect.github.com/nodejs/undici/pull/2309">nodejs/undici#2309</a></li> <li>change default header to <code>node</code> by <a href="https://github.com/Ethan-Arrowood"><code>@Ethan-Arrowood</code></a> in <a href="https://redirect.github.com/nodejs/undici/pull/2310">nodejs/undici#2310</a></li> <li>chore: change order of the pseudo-headers by <a href="https://github.com/kyrylodolynskyi"><code>@kyrylodolynskyi</code></a> in <a href="https://redirect.github.com/nodejs/undici/pull/2308">nodejs/undici#2308</a></li> <li>fix: Agent.Options.factory should accept URL object or string as parameter by <a href="https://github.com/nicole0707"><code>@nicole0707</code></a> in <a href="https://redirect.github.com/nodejs/undici/pull/2295">nodejs/undici#2295</a></li> <li>build(deps-dev): bump sinon from 15.2.0 to 16.1.0 by <a href="https://github.com/dependabot"><code>@dependabot</code></a> in <a href="https://redirect.github.com/nodejs/undici/pull/2312">nodejs/undici#2312</a></li> <li>test: handle npm ignore-scripts settings by <a href="https://github.com/panva"><code>@panva</code></a> in <a href="https://redirect.github.com/nodejs/undici/pull/2313">nodejs/undici#2313</a></li> <li>feat: respect <code>--max-http-header-size</code> Node.js flag by <a href="https://github.com/balazsorban44"><code>@balazsorban44</code></a> in <a href="https://redirect.github.com/nodejs/undici/pull/2234">nodejs/undici#2234</a></li> <li>fix(<a href="https://redirect.github.com/nodejs/undici/issues/2311">#2311</a>): End stream after body sent by <a href="https://github.com/metcoder95"><code>@metcoder95</code></a> in <a href="https://redirect.github.com/nodejs/undici/pull/2314">nodejs/undici#2314</a></li> <li>disallow setting host header in fetch by <a href="https://github.com/KhafraDev"><code>@KhafraDev</code></a> in <a href="https://redirect.github.com/nodejs/undici/pull/2322">nodejs/undici#2322</a></li> <li>[StepSecurity] ci: Harden GitHub Actions by <a href="https://github.com/step-security-bot"><code>@step-security-bot</code></a> in <a href="https://redirect.github.com/nodejs/undici/pull/2325">nodejs/undici#2325</a></li> <li>fix fetch with coverage enabled by <a href="https://github.com/KhafraDev"><code>@KhafraDev</code></a> in <a href="https://redirect.github.com/nodejs/undici/pull/2330">nodejs/undici#2330</a></li> <li>Fix stuck when using http2 POST Buffer by <a href="https://github.com/binsee"><code>@binsee</code></a> in <a href="https://redirect.github.com/nodejs/undici/pull/2336">nodejs/undici#2336</a></li> <li>fix: 🏷️ add allowH2 to BuildOptions by <a href="https://github.com/binsee"><code>@binsee</code></a> in <a href="https://redirect.github.com/nodejs/undici/pull/2334">nodejs/undici#2334</a></li> <li>fix: 🐛 fix process http2 header by <a href="https://github.com/binsee"><code>@binsee</code></a> in <a href="https://redirect.github.com/nodejs/undici/pull/2332">nodejs/undici#2332</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/kyrylodolynskyi"><code>@kyrylodolynskyi</code></a> made their first contribution in <a href="https://redirect.github.com/nodejs/undici/pull/2308">nodejs/undici#2308</a></li> <li><a href="https://github.com/nicole0707"><code>@nicole0707</code></a> made their first contribution in <a href="https://redirect.github.com/nodejs/undici/pull/2295">nodejs/undici#2295</a></li> <li><a href="https://github.com/balazsorban44"><code>@balazsorban44</code></a> made their first contribution in <a href="https://redirect.github.com/nodejs/undici/pull/2234">nodejs/undici#2234</a></li> <li><a href="https://github.com/binsee"><code>@binsee</code></a> made their first contribution in <a href="https://redirect.github.com/nodejs/undici/pull/2336">nodejs/undici#2336</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/nodejs/undici/compare/v5.23.4...v5.26.0">https://github.com/nodejs/undici/compare/v5.23.4...v5.26.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/nodejs/undici/commits/v5.26.2">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/actions/create-github-app-token/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> |
||
|
semantic-release-bot
|
9d97a4282b |
build(release): 1.5.0 [skip ci]
# [1.5.0](https://github.com/actions/create-github-app-token/compare/v1.4.0...v1.5.0) (2023-10-06) ### Features * use dash notation for inputs (deprecates underscore notation) ([#59](https://github.com/actions/create-github-app-token/issues/59)) ([ |
||
|
Clay Miller
|
7b1d2aef87 |
feat: use dash notation for inputs (deprecates underscore notation) (#59)
Fixes #57 This PR implements the 3-step plan proposed by @gr2m in https://github.com/actions/create-github-app-token/issues/57#issuecomment-1751272252: > 1. Support both input types > 2. Log a deprecation warning for the old notation > 3. Add a test for deprecations Although this PR supports both input formats simultaneously, I opted _not_ to document the old format in the updated README. That’s a decision I’m happy to revisit, if y’all would prefer to have documentation for both the old and new formats. |
||
|
Gregor Martynus
|
bdb2377ad0 | test: add coverage (#58) | ||
|
semantic-release-bot
|
8210939678 |
build(release): 1.4.0 [skip ci]
# [1.4.0](https://github.com/actions/create-github-app-token/compare/v1.3.0...v1.4.0) (2023-10-06) ### Features * Add a `skip_token_revoke` input for configuring token revocation ([#54](https://github.com/actions/create-github-app-token/issues/54)) ([ |
||
|
semantic-release-bot
|
d400084c45 |
build(release): 1.3.0 [skip ci]
# [1.3.0](https://github.com/actions/create-github-app-token/compare/v1.2.2...v1.3.0) (2023-10-04) ### Features * support tokens scoped to multiple repositories within organization ([#46](https://github.com/actions/create-github-app-token/issues/46)) ([ |
||
|
semantic-release-bot
|
5804f049e1 |
build(release): 1.2.2 [skip ci]
## [1.2.2](https://github.com/actions/create-github-app-token/compare/v1.2.1...v1.2.2) (2023-10-02) ### Bug Fixes * **deps:** bump the production-dependencies group with 3 updates ([#51](https://github.com/actions/create-github-app-token/issues/51)) ([ |
||
|
dependabot[bot]
|
84daa2c0f0 |
build(deps-dev): bump the development-dependencies group with 2 updates (#52)
Bumps the development-dependencies group with 2 updates: [esbuild](https://github.com/evanw/esbuild) and [undici](https://github.com/nodejs/undici). Updates `esbuild` from 0.19.2 to 0.19.4 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/evanw/esbuild/releases">esbuild's releases</a>.</em></p> <blockquote> <h2>v0.19.4</h2> <ul> <li> <p>Fix printing of JavaScript decorators in tricky cases (<a href="https://redirect.github.com/evanw/esbuild/issues/3396">#3396</a>)</p> <p>This release fixes some bugs where esbuild's pretty-printing of JavaScript decorators could incorrectly produced code with a syntax error. The problem happened because esbuild sometimes substitutes identifiers for other expressions in the pretty-printer itself, but the decision about whether to wrap the expression or not didn't account for this. Here are some examples:</p> <pre lang="js"><code>// Original code import { constant } from './constants.js' import { imported } from 'external' import { undef } from './empty.js' class Foo { @constant() @imported() @undef() foo } <p>// Old output (with --bundle --format=cjs --packages=external --minify-syntax) var import_external = require("external"); var Foo = class { <a href="https://github.com/123"><code>@123</code></a>() @(0, import_external.imported)() @(void 0)() foo; };</p> <p>// New output (with --bundle --format=cjs --packages=external --minify-syntax) var import_external = require("external"); var Foo = class { @(123()) @((0, import_external.imported)()) @((void 0)()) foo; }; </code></pre></p> </li> <li> <p>Allow pre-release versions to be passed to <code>target</code> (<a href="https://redirect.github.com/evanw/esbuild/issues/3388">#3388</a>)</p> <p>People want to be able to pass version numbers for unreleased versions of node (which have extra stuff after the version numbers) to esbuild's <code>target</code> setting and have esbuild do something reasonable with them. These version strings are of course not present in esbuild's internal feature compatibility table because an unreleased version has not been released yet (by definition). With this release, esbuild will now attempt to accept these version strings passed to <code>target</code> and do something reasonable with them.</p> </li> </ul> <h2>v0.19.3</h2> <ul> <li> <p>Fix <code>list-style-type</code> with the <code>local-css</code> loader (<a href="https://redirect.github.com/evanw/esbuild/issues/3325">#3325</a>)</p> <p>The <code>local-css</code> loader incorrectly treated all identifiers provided to <code>list-style-type</code> as a custom local identifier. That included identifiers such as <code>none</code> which have special meaning in CSS, and which should not be treated as custom local identifiers. This release fixes this bug:</p> <pre lang="css"><code>/* Original code */ ul { list-style-type: none } <p>/* Old output (with --loader=local-css) */ </code></pre></p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/evanw/esbuild/blob/main/CHANGELOG.md">esbuild's changelog</a>.</em></p> <blockquote> <h2>0.19.4</h2> <ul> <li> <p>Fix printing of JavaScript decorators in tricky cases (<a href="https://redirect.github.com/evanw/esbuild/issues/3396">#3396</a>)</p> <p>This release fixes some bugs where esbuild's pretty-printing of JavaScript decorators could incorrectly produced code with a syntax error. The problem happened because esbuild sometimes substitutes identifiers for other expressions in the pretty-printer itself, but the decision about whether to wrap the expression or not didn't account for this. Here are some examples:</p> <pre lang="js"><code>// Original code import { constant } from './constants.js' import { imported } from 'external' import { undef } from './empty.js' class Foo { @constant() @imported() @undef() foo } <p>// Old output (with --bundle --format=cjs --packages=external --minify-syntax) var import_external = require("external"); var Foo = class { <a href="https://github.com/123"><code>@123</code></a>() @(0, import_external.imported)() @(void 0)() foo; };</p> <p>// New output (with --bundle --format=cjs --packages=external --minify-syntax) var import_external = require("external"); var Foo = class { @(123()) @((0, import_external.imported)()) @((void 0)()) foo; }; </code></pre></p> </li> <li> <p>Allow pre-release versions to be passed to <code>target</code> (<a href="https://redirect.github.com/evanw/esbuild/issues/3388">#3388</a>)</p> <p>People want to be able to pass version numbers for unreleased versions of node (which have extra stuff after the version numbers) to esbuild's <code>target</code> setting and have esbuild do something reasonable with them. These version strings are of course not present in esbuild's internal feature compatibility table because an unreleased version has not been released yet (by definition). With this release, esbuild will now attempt to accept these version strings passed to <code>target</code> and do something reasonable with them.</p> </li> </ul> <h2>0.19.3</h2> <ul> <li> <p>Fix <code>list-style-type</code> with the <code>local-css</code> loader (<a href="https://redirect.github.com/evanw/esbuild/issues/3325">#3325</a>)</p> <p>The <code>local-css</code> loader incorrectly treated all identifiers provided to <code>list-style-type</code> as a custom local identifier. That included identifiers such as <code>none</code> which have special meaning in CSS, and which should not be treated as custom local identifiers. This release fixes this bug:</p> <pre lang="css"><code>/* Original code */ ul { list-style-type: none } </code></pre> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
dependabot[bot]
|
6d98b259d9 |
fix(deps): bump the production-dependencies group with 3 updates (#51)
Bumps the production-dependencies group with 3 updates: [@actions/core](https://github.com/actions/toolkit/tree/HEAD/packages/core), [@octokit/auth-app](https://github.com/octokit/auth-app.js) and [@octokit/request](https://github.com/octokit/request.js). Updates `@actions/core` from 1.10.0 to 1.10.1 <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/actions/toolkit/blob/main/packages/core/RELEASES.md"><code>@actions/core</code>'s changelog</a>.</em></p> <blockquote> <h3>1.10.1</h3> <ul> <li>Fix error message reference in oidc utils <a href="https://redirect.github.com/actions/toolkit/pull/1511">#1511</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/actions/toolkit/commits/HEAD/packages/core">compare view</a></li> </ul> </details> <br /> Updates `@octokit/auth-app` from 6.0.0 to 6.0.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/octokit/auth-app.js/releases"><code>@octokit/auth-app</code>'s releases</a>.</em></p> <blockquote> <h2>v6.0.1</h2> <h2><a href="https://github.com/octokit/auth-app.js/compare/v6.0.0...v6.0.1">6.0.1</a> (2023-09-23)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>deps:</strong> update dependency <code>@octokit/types</code> to v12 (<a href="https://redirect.github.com/octokit/auth-app.js/issues/535">#535</a>) (<a href=" |
||
|
Parker Brown
|
10f155294b |
test: integration tests (#40)
Co-authored-by: Gregor Martynus <39992+gr2m@users.noreply.github.com> |
||
|
semantic-release-bot
|
49ce228ea7 |
build(release): 1.2.1 [skip ci]
## [1.2.1](https://github.com/actions/create-github-app-token/compare/v1.2.0...v1.2.1) (2023-08-30) ### Bug Fixes * **GHES:** respect `GITHUB_API_URL` when creating installation access token ([#38](https://github.com/actions/create-github-app-token/issues/38)) ([ |
||
|
semantic-release-bot
|
c72844caa4 |
build(release): 1.2.0 [skip ci]
# [1.2.0](https://github.com/actions/create-github-app-token/compare/v1.1.5...v1.2.0) (2023-08-29) ### Features * add GitHub Enterprise Server (GHES) support ([#36](https://github.com/actions/create-github-app-token/issues/36)) ([ |
||
|
semantic-release-bot
|
17cde8a7d8 |
build(release): 1.1.5 [skip ci]
## [1.1.5](https://github.com/actions/create-github-app-token/compare/v1.1.4...v1.1.5) (2023-08-28) ### Bug Fixes * **release:** update version in `package.json` ([#35](https://github.com/actions/create-github-app-token/issues/35)) ([ |
||
|
Gregor Martynus
|
1dccc4ccc6 |
fix(release): update version in package.json (#35)
closes #34 Co-authored-by: Parker Brown <17183625+parkerbxyz@users.noreply.github.com> |
||
|
Gregor Martynus
|
b287cb86e2 |
fix(deps): update @octokit packages to latest (#24)
|
||
|
dependabot[bot]
|
73a9531b26 |
build(deps-dev): bump dotenv from 16.0.3 to 16.3.1 (#18)
[//]: # (dependabot-start) ⚠️ **Dependabot is rebasing this PR** ⚠️ Rebasing might not happen immediately, so don't worry if this takes some time. Note: if you make any changes to this PR yourself, they will take precedence over the rebase. --- [//]: # (dependabot-end) Bumps [dotenv](https://github.com/motdotla/dotenv) from 16.0.3 to 16.3.1. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/motdotla/dotenv/blob/master/CHANGELOG.md">dotenv's changelog</a>.</em></p> <blockquote> <h2><a href="https://github.com/motdotla/dotenv/compare/v16.3.0...v16.3.1">16.3.1</a> (2023-06-17)</h2> <h3>Added</h3> <ul> <li>Add missing type definitions for <code>processEnv</code> and <code>DOTENV_KEY</code> options. <a href="https://redirect.github.com/motdotla/dotenv/pull/756">#756</a></li> </ul> <h2><a href="https://github.com/motdotla/dotenv/compare/v16.2.0...v16.3.0">16.3.0</a> (2023-06-16)</h2> <h3>Added</h3> <ul> <li>Optionally pass <code>DOTENV_KEY</code> to options rather than relying on <code>process.env.DOTENV_KEY</code>. Defaults to <code>process.env.DOTENV_KEY</code> <a href="https://redirect.github.com/motdotla/dotenv/pull/754">#754</a></li> </ul> <h2><a href="https://github.com/motdotla/dotenv/compare/v16.1.4...v16.2.0">16.2.0</a> (2023-06-15)</h2> <h3>Added</h3> <ul> <li>Optionally write to your own target object rather than <code>process.env</code>. Defaults to <code>process.env</code>. <a href="https://redirect.github.com/motdotla/dotenv/pull/753">#753</a></li> <li>Add import type URL to types file <a href="https://redirect.github.com/motdotla/dotenv/pull/751">#751</a></li> </ul> <h2><a href="https://github.com/motdotla/dotenv/compare/v16.1.3...v16.1.4">16.1.4</a> (2023-06-04)</h2> <h3>Added</h3> <ul> <li>Added <code>.github/</code> to <code>.npmignore</code> <a href="https://redirect.github.com/motdotla/dotenv/pull/747">#747</a></li> </ul> <h2><a href="https://github.com/motdotla/dotenv/compare/v16.1.2...v16.1.3">16.1.3</a> (2023-05-31)</h2> <h3>Removed</h3> <ul> <li>Removed <code>browser</code> keys for <code>path</code>, <code>os</code>, and <code>crypto</code> in package.json. These were set to false incorrectly as of 16.1. Instead, if using dotenv on the front-end make sure to include polyfills for <code>path</code>, <code>os</code>, and <code>crypto</code>. <a href="https://github.com/Richienb/node-polyfill-webpack-plugin">node-polyfill-webpack-plugin</a> provides these.</li> </ul> <h2><a href="https://github.com/motdotla/dotenv/compare/v16.1.1...v16.1.2">16.1.2</a> (2023-05-31)</h2> <h3>Changed</h3> <ul> <li>Exposed private function <code>_configDotenv</code> as <code>configDotenv</code>. <a href="https://redirect.github.com/motdotla/dotenv/pull/744">#744</a></li> </ul> <h2><a href="https://github.com/motdotla/dotenv/compare/v16.1.0...v16.1.1">16.1.1</a> (2023-05-30)</h2> <h3>Added</h3> <ul> <li>Added type definition for <code>decrypt</code> function</li> </ul> <h3>Changed</h3> <ul> <li>Fixed <code>{crypto: false}</code> in <code>packageJson.browser</code></li> </ul> <h2><a href="https://github.com/motdotla/dotenv/compare/v16.0.3...v16.1.0">16.1.0</a> (2023-05-30)</h2> <h3>Added</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
dependabot[bot]
|
1fc9983a3b |
build(deps-dev): bump esbuild from 0.17.19 to 0.19.2 (#19)
Bumps [esbuild](https://github.com/evanw/esbuild) from 0.17.19 to 0.19.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/evanw/esbuild/releases">esbuild's releases</a>.</em></p> <blockquote> <h2>v0.19.2</h2> <ul> <li> <p>Update how CSS nesting is parsed again</p> <p>CSS nesting syntax has been changed again, and esbuild has been updated to match. Type selectors may now be used with CSS nesting:</p> <pre lang="css"><code>.foo { div { color: red; } } </code></pre> <p>Previously this was disallowed in the CSS specification because it's ambiguous whether an identifier is a declaration or a nested rule starting with a type selector without requiring unbounded lookahead in the parser. It has now been allowed because the CSS working group has decided that requiring unbounded lookahead is acceptable after all.</p> <p>Note that this change means esbuild no longer considers any existing browser to support CSS nesting since none of the existing browsers support this new syntax. CSS nesting will now always be transformed when targeting a browser. This situation will change in the future as browsers add support for this new syntax.</p> </li> <li> <p>Fix a scope-related bug with <code>--drop-labels=</code> (<a href="https://redirect.github.com/evanw/esbuild/issues/3311">#3311</a>)</p> <p>The recently-released <code>--drop-labels=</code> feature previously had a bug where esbuild's internal scope stack wasn't being restored properly when a statement with a label was dropped. This could manifest as a tree-shaking issue, although it's possible that this could have also been causing other subtle problems too. The bug has been fixed in this release.</p> </li> <li> <p>Make renamed CSS names unique across entry points (<a href="https://redirect.github.com/evanw/esbuild/issues/3295">#3295</a>)</p> <p>Previously esbuild's generated names for local names in CSS were only unique within a given entry point (or across all entry points when code splitting was enabled). That meant that building multiple entry points with esbuild could result in local names being renamed to the same identifier even when those entry points were built simultaneously within a single esbuild API call. This problem was especially likely to happen with minification enabled. With this release, esbuild will now avoid renaming local names from two separate entry points to the same name if those entry points were built with a single esbuild API call, even when code splitting is disabled.</p> </li> <li> <p>Fix CSS ordering bug with <code>@layer</code> before <code>@import</code></p> <p>CSS lets you put <code>@layer</code> rules before <code>@import</code> rules to define the order of layers in a stylesheet. Previously esbuild's CSS bundler incorrectly ordered these after the imported files because before the introduction of cascade layers to CSS, imported files could be bundled by removing the <code>@import</code> rules and then joining files together in the right order. But with <code>@layer</code>, CSS files may now need to be split apart into multiple pieces in the bundle. For example:</p> <pre><code>/* Original code */ @layer start; @import "data:text/css,@layer inner.start;"; @import "data:text/css,@layer inner.end;"; @layer end; <p>/* Old output (with --bundle) */ <a href="https://github.com/layer"><code>@layer</code></a> inner.start; <a href="https://github.com/layer"><code>@layer</code></a> inner.end; <a href="https://github.com/layer"><code>@layer</code></a> start; <a href="https://github.com/layer"><code>@layer</code></a> end;</p> <p>/* New output (with --bundle) */ <a href="https://github.com/layer"><code>@layer</code></a> start; <a href="https://github.com/layer"><code>@layer</code></a> inner.start; <a href="https://github.com/layer"><code>@layer</code></a> inner.end; <a href="https://github.com/layer"><code>@layer</code></a> end; </code></pre></p> </li> <li> <p>Unwrap nested duplicate <code>@media</code> rules (<a href="https://redirect.github.com/evanw/esbuild/issues/3226">#3226</a>)</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/evanw/esbuild/blob/main/CHANGELOG.md">esbuild's changelog</a>.</em></p> <blockquote> <h2>0.19.2</h2> <ul> <li> <p>Update how CSS nesting is parsed again</p> <p>CSS nesting syntax has been changed again, and esbuild has been updated to match. Type selectors may now be used with CSS nesting:</p> <pre lang="css"><code>.foo { div { color: red; } } </code></pre> <p>Previously this was disallowed in the CSS specification because it's ambiguous whether an identifier is a declaration or a nested rule starting with a type selector without requiring unbounded lookahead in the parser. It has now been allowed because the CSS working group has decided that requiring unbounded lookahead is acceptable after all.</p> <p>Note that this change means esbuild no longer considers any existing browser to support CSS nesting since none of the existing browsers support this new syntax. CSS nesting will now always be transformed when targeting a browser. This situation will change in the future as browsers add support for this new syntax.</p> </li> <li> <p>Fix a scope-related bug with <code>--drop-labels=</code> (<a href="https://redirect.github.com/evanw/esbuild/issues/3311">#3311</a>)</p> <p>The recently-released <code>--drop-labels=</code> feature previously had a bug where esbuild's internal scope stack wasn't being restored properly when a statement with a label was dropped. This could manifest as a tree-shaking issue, although it's possible that this could have also been causing other subtle problems too. The bug has been fixed in this release.</p> </li> <li> <p>Make renamed CSS names unique across entry points (<a href="https://redirect.github.com/evanw/esbuild/issues/3295">#3295</a>)</p> <p>Previously esbuild's generated names for local names in CSS were only unique within a given entry point (or across all entry points when code splitting was enabled). That meant that building multiple entry points with esbuild could result in local names being renamed to the same identifier even when those entry points were built simultaneously within a single esbuild API call. This problem was especially likely to happen with minification enabled. With this release, esbuild will now avoid renaming local names from two separate entry points to the same name if those entry points were built with a single esbuild API call, even when code splitting is disabled.</p> </li> <li> <p>Fix CSS ordering bug with <code>@layer</code> before <code>@import</code></p> <p>CSS lets you put <code>@layer</code> rules before <code>@import</code> rules to define the order of layers in a stylesheet. Previously esbuild's CSS bundler incorrectly ordered these after the imported files because before the introduction of cascade layers to CSS, imported files could be bundled by removing the <code>@import</code> rules and then joining files together in the right order. But with <code>@layer</code>, CSS files may now need to be split apart into multiple pieces in the bundle. For example:</p> <pre><code>/* Original code */ @layer start; @import "data:text/css,@layer inner.start;"; @import "data:text/css,@layer inner.end;"; @layer end; <p>/* Old output (with --bundle) */ <a href="https://github.com/layer"><code>@layer</code></a> inner.start; <a href="https://github.com/layer"><code>@layer</code></a> inner.end; <a href="https://github.com/layer"><code>@layer</code></a> start; <a href="https://github.com/layer"><code>@layer</code></a> end;</p> <p>/* New output (with --bundle) */ <a href="https://github.com/layer"><code>@layer</code></a> start; <a href="https://github.com/layer"><code>@layer</code></a> inner.start; <a href="https://github.com/layer"><code>@layer</code></a> inner.end; <a href="https://github.com/layer"><code>@layer</code></a> end; </code></pre></p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
Gregor Martynus
|
9cf7227dfb | ci(release): set version on release and push using git plugin (#22) | ||
|
Gregor Martynus
|
847634eeb3 |
fix(ci): release configuration (#6)
Some checks failed
/ demo (push) Has been cancelled
|
||
|
Gregor Martynus
|
f45685208f |
feat: initial version (#1)
Some checks failed
/ demo (push) Has been cancelled
Co-authored-by: Parker Brown <17183625+parkerbxyz@users.noreply.github.com> Co-authored-by: Gregor Martynus <gr2m@users.noreply.github.com> |