github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-07 21:30:36 -05:00
Code Issues 564 Packages Projects Releases 72 Wiki Activity

[PR #823] [MERGED] Bump esbuild and drizzle-kit #7134

New Issue
Closed
opened 2026-04-25 16:05:30 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-25 16:05:30 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/fosrl/pangolin/pull/823
Author: @dependabot[bot]
Created: 6/2/2025
Status: ✅ Merged
Merged: 6/2/2025
Merged by: @oschwartz10612

Base: main ← Head: dependabot/npm_and_yarn/multi-5726d3b8f4

📝 Commits (1)

  • 80375cd Bump esbuild and drizzle-kit

📊 Changes

2 files changed (+67 additions, -503 deletions)

View changed files

📝 package-lock.json (+66 -502)
📝 package.json (+1 -1)

📄 Description

Bumps esbuild to 0.25.2 and updates ancestor dependency drizzle-kit. These dependencies need to be updated together.

Updates esbuild from 0.18.20 to 0.25.2

Release notes

Sourced from esbuild's releases.

v0.25.2

  • Support flags in regular expressions for the API (#4121)

    The JavaScript plugin API for esbuild takes JavaScript regular expression objects for the filter option. Internally these are translated into Go regular expressions. However, this translation previously ignored the flags property of the regular expression. With this release, esbuild will now translate JavaScript regular expression flags into Go regular expression flags. Specifically the JavaScript regular expression /\.[jt]sx?$/i is turned into the Go regular expression `(?i)\.[jt]sx?$` internally inside of esbuild's API. This should make it possible to use JavaScript regular expressions with the i flag. Note that JavaScript and Go don't support all of the same regular expression features, so this mapping is only approximate.

  • Fix node-specific annotations for string literal export names (#4100)

    When node instantiates a CommonJS module, it scans the AST to look for names to expose via ESM named exports. This is a heuristic that looks for certain patterns such as exports.NAME = ... or module.exports = { ... }. This behavior is used by esbuild to "annotate" CommonJS code that was converted from ESM with the original ESM export names. For example, when converting the file export let foo, bar from ESM to CommonJS, esbuild appends this to the end of the file:

    // Annotate the CommonJS export names for ESM import in node:
0 && (module.exports = {
  bar,
  foo
});

    However, this feature previously didn't work correctly for export names that are not valid identifiers, which can be constructed using string literal export names. The generated code contained a syntax error. That problem is fixed in this release:

    // Original code
let foo
export { foo as "foo!" }

    // Old output (with --format=cjs --platform=node)
...
0 && (module.exports = {
"foo!"
});
    

    // New output (with --format=cjs --platform=node)
...
0 && (module.exports = {
"foo!": null
});

  • Basic support for index source maps (#3439, #4109)

    The source map specification has an optional mode called index source maps that makes it easier for tools to create an aggregate JavaScript file by concatenating many smaller JavaScript files with source maps, and then generate an aggregate source map by simply providing the original source maps along with some offset information. My understanding is that this is rarely used in practice. I'm only aware of two uses of it in the wild: ClojureScript and Turbopack.

    This release provides basic support for indexed source maps. However, the implementation has not been tested on a real app (just on very simple test input). If you are using index source maps in a real app, please try this out and report back if anything isn't working for you.

    Note that this is also not a complete implementation. For example, index source maps technically allows nesting source maps to an arbitrary depth, while esbuild's implementation in this release only supports a single level of nesting. It's unclear whether supporting more than one level of nesting is important or not given the lack of available test cases.

    This feature was contributed by @​clyfish.

v0.25.1

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2023

This changelog documents all esbuild versions published in the year 2023 (versions 0.16.13 through 0.19.11).

0.19.11

  • Fix TypeScript-specific class transform edge case (#3559)

    The previous release introduced an optimization that avoided transforming super() in the class constructor for TypeScript code compiled with useDefineForClassFields set to false if all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case and there are #private instance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call to super() (since super() is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:

    // Original code
class Foo extends Bar {
  #private = 1;
  public: any;
  constructor() {
    super();
  }
}

    // Old output (with esbuild v0.19.9)
class Foo extends Bar {
constructor() {
super();
this.#private = 1;
}
#private;
}
    

    // Old output (with esbuild v0.19.10)
class Foo extends Bar {
constructor() {
this.#private = 1;
super();
}
#private;
}
    

    // New output
class Foo extends Bar {
#private = 1;
constructor() {
super();
}
}

  • Minifier: allow reording a primitive past a side-effect (#3568)

    The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:

... (truncated)

Commits

Updates drizzle-kit from 0.30.6 to 0.31.1

Release notes

Sourced from drizzle-kit's releases.

drizzle-kit@0.31.1

Fixed drizzle-kit pull bugs when using Gel extensions.

Because Gel extensions create schema names containing :: (for example, ext::auth), Drizzle previously handled these names incorrectly. Starting with this release, you can use Gel extensions without any problems. Here’s what you should do:

  1. Enable extensions schemas in drizzle.config.ts
import  { defineConfig } from "drizzle-kit";

export default defineConfig({
dialect: 'gel',
schemaFilter: ['ext::auth', 'public']
});

  1. Run drizzle-kit pull

  2. Done!

drizzle-kit@0.31.0

Features and improvements

Enum DDL improvements

For situations where you drop an enum value or reorder values in an enum, there is no native way to do this in PostgreSQL. To handle these cases, drizzle-kit used to:

  • Change the column data types from the enum to text
  • Drop the old enum
  • Add the new enum
  • Change the column data types back to the new enum

However, there were a few scenarios that weren’t covered: PostgreSQL wasn’t updating default expressions for columns when their data types changed

Therefore, for cases where you either change a column’s data type from an enum to some other type, drop an enum value, or reorder enum values, we now do the following:

  • Change the column data types from the enum to text
  • Set the default using the ::text expression
  • Drop the old enum
  • Add the new enum
  • Change the column data types back to the new enum
  • Set the default using the :: expression

esbuild version upgrade

For drizzle-kit we upgraded the version to latest (0.25.2), thanks @​paulmarsicloud

Bug fixes

... (truncated)

Commits

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 commands and options

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.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/fosrl/pangolin/pull/823 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 6/2/2025 **Status:** ✅ Merged **Merged:** 6/2/2025 **Merged by:** [@oschwartz10612](https://github.com/oschwartz10612) **Base:** `main` ← **Head:** `dependabot/npm_and_yarn/multi-5726d3b8f4` --- ### 📝 Commits (1) - [`80375cd`](https://github.com/fosrl/pangolin/commit/80375cd0dcfef46a20c3e43239aacf94e937e57c) Bump esbuild and drizzle-kit ### 📊 Changes **2 files changed** (+67 additions, -503 deletions) <details> <summary>View changed files</summary> 📝 `package-lock.json` (+66 -502) 📝 `package.json` (+1 -1) </details> ### 📄 Description Bumps [esbuild](https://github.com/evanw/esbuild) to 0.25.2 and updates ancestor dependency [drizzle-kit](https://github.com/drizzle-team/drizzle-orm). These dependencies need to be updated together. Updates `esbuild` from 0.18.20 to 0.25.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.25.2</h2> <ul> <li> <p>Support flags in regular expressions for the API (<a href="https://redirect.github.com/evanw/esbuild/issues/4121">#4121</a>)</p> <p>The JavaScript plugin API for esbuild takes JavaScript regular expression objects for the <code>filter</code> option. Internally these are translated into Go regular expressions. However, this translation previously ignored the <code>flags</code> property of the regular expression. With this release, esbuild will now translate JavaScript regular expression flags into Go regular expression flags. Specifically the JavaScript regular expression <code>/\.[jt]sx?$/i</code> is turned into the Go regular expression <code>`(?i)\.[jt]sx?$`</code> internally inside of esbuild's API. This should make it possible to use JavaScript regular expressions with the <code>i</code> flag. Note that JavaScript and Go don't support all of the same regular expression features, so this mapping is only approximate.</p> </li> <li> <p>Fix node-specific annotations for string literal export names (<a href="https://redirect.github.com/evanw/esbuild/issues/4100">#4100</a>)</p> <p>When node instantiates a CommonJS module, it scans the AST to look for names to expose via ESM named exports. This is a heuristic that looks for certain patterns such as <code>exports.NAME = ...</code> or <code>module.exports = { ... }</code>. This behavior is used by esbuild to &quot;annotate&quot; CommonJS code that was converted from ESM with the original ESM export names. For example, when converting the file <code>export let foo, bar</code> from ESM to CommonJS, esbuild appends this to the end of the file:</p> <pre lang="js"><code>// Annotate the CommonJS export names for ESM import in node: 0 &amp;&amp; (module.exports = { bar, foo }); </code></pre> <p>However, this feature previously didn't work correctly for export names that are not valid identifiers, which can be constructed using string literal export names. The generated code contained a syntax error. That problem is fixed in this release:</p> <pre lang="js"><code>// Original code let foo export { foo as &quot;foo!&quot; } <p>// Old output (with --format=cjs --platform=node) ... 0 &amp;&amp; (module.exports = { &quot;foo!&quot; });</p> <p>// New output (with --format=cjs --platform=node) ... 0 &amp;&amp; (module.exports = { &quot;foo!&quot;: null }); </code></pre></p> </li> <li> <p>Basic support for index source maps (<a href="https://redirect.github.com/evanw/esbuild/issues/3439">#3439</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4109">#4109</a>)</p> <p>The source map specification has an optional mode called <a href="https://tc39.es/ecma426/#sec-index-source-map">index source maps</a> that makes it easier for tools to create an aggregate JavaScript file by concatenating many smaller JavaScript files with source maps, and then generate an aggregate source map by simply providing the original source maps along with some offset information. My understanding is that this is rarely used in practice. I'm only aware of two uses of it in the wild: <a href="https://clojurescript.org/">ClojureScript</a> and <a href="https://turbo.build/pack/">Turbopack</a>.</p> <p>This release provides basic support for indexed source maps. However, the implementation has not been tested on a real app (just on very simple test input). If you are using index source maps in a real app, please try this out and report back if anything isn't working for you.</p> <p>Note that this is also not a complete implementation. For example, index source maps technically allows nesting source maps to an arbitrary depth, while esbuild's implementation in this release only supports a single level of nesting. It's unclear whether supporting more than one level of nesting is important or not given the lack of available test cases.</p> <p>This feature was contributed by <a href="https://github.com/clyfish"><code>@​clyfish</code></a>.</p> </li> </ul> <h2>v0.25.1</h2> <ul> <li>Fix incorrect paths in inline source maps (<a href="https://redirect.github.com/evanw/esbuild/issues/4070">#4070</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/4075">#4075</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/4105">#4105</a>)</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-2023.md">esbuild's changelog</a>.</em></p> <blockquote> <h1>Changelog: 2023</h1> <p>This changelog documents all esbuild versions published in the year 2023 (versions 0.16.13 through 0.19.11).</p> <h2>0.19.11</h2> <ul> <li> <p>Fix TypeScript-specific class transform edge case (<a href="https://redirect.github.com/evanw/esbuild/issues/3559">#3559</a>)</p> <p>The previous release introduced an optimization that avoided transforming <code>super()</code> in the class constructor for TypeScript code compiled with <code>useDefineForClassFields</code> set to <code>false</code> if all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case <em>and</em> there are <code>#private</code> instance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call to <code>super()</code> (since <code>super()</code> is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:</p> <pre lang="ts"><code>// Original code class Foo extends Bar { #private = 1; public: any; constructor() { super(); } } <p>// Old output (with esbuild v0.19.9) class Foo extends Bar { constructor() { super(); this.#private = 1; } #private; }</p> <p>// Old output (with esbuild v0.19.10) class Foo extends Bar { constructor() { this.#private = 1; super(); } #private; }</p> <p>// New output class Foo extends Bar { #private = 1; constructor() { super(); } } </code></pre></p> </li> <li> <p>Minifier: allow reording a primitive past a side-effect (<a href="https://redirect.github.com/evanw/esbuild/issues/3568">#3568</a>)</p> <p>The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/evanw/esbuild/commit/4475787eef4c4923b92b9fa37ebba1c88b9e1d9b"><code>4475787</code></a> publish 0.25.2 to npm</li> <li><a href="https://github.com/evanw/esbuild/commit/8f56771afc37c2b328056a2e6aefdfc2b821c5d7"><code>8f56771</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4121">#4121</a>: map js regexp flags to go regexp flags</li> <li><a href="https://github.com/evanw/esbuild/commit/36b458d144796882a78baaa40baac5f88c7694b1"><code>36b458d</code></a> follow-up to <a href="https://redirect.github.com/evanw/esbuild/issues/4109">#4109</a></li> <li><a href="https://github.com/evanw/esbuild/commit/8b8437cb0fccd680ef39548fc7bb56ff8f48333d"><code>8b8437c</code></a> feat: support index source map (<a href="https://redirect.github.com/evanw/esbuild/issues/4109">#4109</a>)</li> <li><a href="https://github.com/evanw/esbuild/commit/75286c1b4fabcf93140b97c3c0488f0253158b47"><code>75286c1</code></a> unit test for absolute windows paths in source map</li> <li><a href="https://github.com/evanw/esbuild/commit/bcc77fbee56ec7c050813c972d8bb1e06a8e57ef"><code>bcc77fb</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4100">#4100</a>: invalid identifiers in node annotation</li> <li><a href="https://github.com/evanw/esbuild/commit/37cb6a2bc3da13e7805a57782ced720fda7eb1f7"><code>37cb6a2</code></a> fix a warning from <code>npm publish</code></li> <li><a href="https://github.com/evanw/esbuild/commit/6bfc1c13b4d986b86e8bc2035f00c337b0c1d007"><code>6bfc1c1</code></a> publish 0.25.1 to npm</li> <li><a href="https://github.com/evanw/esbuild/commit/f9b39529a328f513cd73b36e8488a4a624df5c36"><code>f9b3952</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4078">#4078</a>: prepend namespaces to source map paths</li> <li><a href="https://github.com/evanw/esbuild/commit/ccf3dd7889e7765a1d6f1596ada0f22b320d7174"><code>ccf3dd7</code></a> add &quot;contributed by&quot; in changelog</li> <li>Additional commits viewable in <a href="https://github.com/evanw/esbuild/compare/v0.18.20...v0.25.2">compare view</a></li> </ul> </details> <br /> Updates `drizzle-kit` from 0.30.6 to 0.31.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/drizzle-team/drizzle-orm/releases">drizzle-kit's releases</a>.</em></p> <blockquote> <h2>drizzle-kit@0.31.1</h2> <h3>Fixed <code>drizzle-kit pull</code> bugs when using Gel extensions.</h3> <p>Because Gel extensions create schema names containing <code>::</code> (for example, <code>ext::auth</code>), Drizzle previously handled these names incorrectly. Starting with this release, you can use Gel extensions without any problems. Here’s what you should do:</p> <ol> <li>Enable extensions schemas in <code>drizzle.config.ts</code></li> </ol> <pre lang="ts"><code>import { defineConfig } from &quot;drizzle-kit&quot;; <p>export default defineConfig({ dialect: 'gel', schemaFilter: ['ext::auth', 'public'] }); </code></pre></p> <ol start="2"> <li> <p>Run <code>drizzle-kit pull</code></p> </li> <li> <p>Done!</p> </li> </ol> <h2>drizzle-kit@0.31.0</h2> <h2>Features and improvements</h2> <h3>Enum DDL improvements</h3> <p>For situations where you drop an <code>enum</code> value or reorder values in an <code>enum</code>, there is no native way to do this in PostgreSQL. To handle these cases, <code>drizzle-kit</code> used to:</p> <ul> <li>Change the column data types from the enum to text</li> <li>Drop the old enum</li> <li>Add the new enum</li> <li>Change the column data types back to the new enum</li> </ul> <p>However, there were a few scenarios that weren’t covered: <code>PostgreSQL</code> wasn’t updating default expressions for columns when their data types changed</p> <p>Therefore, for cases where you either change a column’s data type from an <code>enum</code> to some other type, drop an <code>enum</code> value, or reorder <code>enum</code> values, we now do the following:</p> <ul> <li>Change the column data types from the enum to text</li> <li>Set the default using the ::text expression</li> <li>Drop the old enum</li> <li>Add the new enum</li> <li>Change the column data types back to the new enum</li> <li>Set the default using the ::<!-- raw HTML omitted --> expression</li> </ul> <h3><code>esbuild</code> version upgrade</h3> <p>For <code>drizzle-kit</code> we upgraded the version to latest (<code>0.25.2</code>), thanks <a href="https://github.com/paulmarsicloud"><code>@​paulmarsicloud</code></a></p> <h2>Bug fixes</h2> <ul> <li><a href="https://redirect.github.com/drizzle-team/drizzle-orm/issues/2715">[BUG]: Error on Malformed Array Literal</a> - thanks <a href="https://github.com/Kratious"><code>@​Kratious</code></a></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/drizzle-team/drizzle-orm/commit/efb40fee413c2728af7bb2ad154aaecad151ff04"><code>efb40fe</code></a> Add fix for Gel Schemas (<a href="https://redirect.github.com/drizzle-team/drizzle-orm/issues/4483">#4483</a>)</li> <li><a href="https://github.com/drizzle-team/drizzle-orm/commit/ad28dcd494d043fc39fa15a1622bb7a51deb6090"><code>ad28dcd</code></a> Fixed <code>pgSchema</code> enum types (fixes <a href="https://redirect.github.com/drizzle-team/drizzle-orm/issues/4421">#4421</a>) (<a href="https://redirect.github.com/drizzle-team/drizzle-orm/issues/4450">#4450</a>)</li> <li><a href="https://github.com/drizzle-team/drizzle-orm/commit/2263c3c67cdba6eb59c74c3d6965ffaaf0cee12e"><code>2263c3c</code></a> v0.43.0 (<a href="https://redirect.github.com/drizzle-team/drizzle-orm/issues/4397">#4397</a>)</li> <li><a href="https://github.com/drizzle-team/drizzle-orm/commit/9e81def6dbe33e54ef96f5960cf87ec829b7414f"><code>9e81def</code></a> Update CI/CD to 22.04</li> <li><a href="https://github.com/drizzle-team/drizzle-orm/commit/df6d5f78c4e72fe91f1f88d7cdf15bcf5be5322c"><code>df6d5f7</code></a> 0.41 (<a href="https://redirect.github.com/drizzle-team/drizzle-orm/issues/4416">#4416</a>)</li> <li><a href="https://github.com/drizzle-team/drizzle-orm/commit/6ab1bbea566f3e2e048c6980038696e03d8e780a"><code>6ab1bbe</code></a> Add Arktype validation (via <code>drizzle-arktype</code> package) (<a href="https://redirect.github.com/drizzle-team/drizzle-orm/issues/4314">#4314</a>)</li> <li>See full diff in <a href="https://github.com/drizzle-team/drizzle-orm/compare/drizzle-kit@0.30.6...drizzle-kit@0.31.1">compare view</a></li> </ul> </details> <br /> 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/fosrl/pangolin/network/alerts). </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-25 16:05:30 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#7134
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?