Fix branch name in versioning.js comment: 'main' → 'master' (#1346)

Copilot · Azgaar · web-flow · commit ab445d910e2a · 2026-03-07T17:03:50.000+01:00
* Initial plan

* fix: update branch name in versioning.js comment from 'main' to 'master'

Co-authored-by: Azgaar &lt;26469650+Azgaar@users.noreply.github.com&gt;

---------

Co-authored-by: copilot-swe-agent[bot] &lt;198982749+Copilot@users.noreply.github.com&gt;
Co-authored-by: Azgaar &lt;26469650+Azgaar@users.noreply.github.com&gt;
diff --git a/public/versioning.js b/public/versioning.js
@@ -5,7 +5,7 @@
  * We use Semantic Versioning: major.minor.patch. Refer to https://semver.org
  * Our .map file format is considered the public API.
  *
- * Update the version on each merge to main:
+ * Update the version on each merge to master:
  * 1. MAJOR version: Incompatible changes that break existing maps
  * 2. MINOR version: Additions or changes that are backward-compatible but may require old .map files to be updated
  * 3. PATCH version: Backward-compatible bug fixes and small features that don't affect the .map file format

Original file line number	Diff line number	Diff line change
`@@ -5,7 +5,7 @@`
`5`	`5`	`* We use Semantic Versioning: major.minor.patch. Refer to https://semver.org`
`6`	`6`	`* Our .map file format is considered the public API.`
`7`	`7`	`*`
`8`		`- * Update the version on each merge to main:`
	`8`	`+ * Update the version on each merge to master:`
`9`	`9`	`* 1. MAJOR version: Incompatible changes that break existing maps`
`10`	`10`	`* 2. MINOR version: Additions or changes that are backward-compatible but may require old .map files to be updated`
`11`	`11`	`* 3. PATCH version: Backward-compatible bug fixes and small features that don't affect the .map file format`