@ferrflow/doc 7.28.0 → 7.28.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/data/benchmarks.json +698 -698
- package/docs-en/reference/errors.md +581 -74
- package/docs-fr/reference/errors.md +654 -20
- package/package.json +1 -1
|
@@ -121,6 +121,42 @@ More than one config file was found in the project root (e.g. both `ferrflow.jso
|
|
|
121
121
|
|
|
122
122
|
Running `ferrflow init` when a config file already exists.
|
|
123
123
|
|
|
124
|
+
### E1018: Path outside the repository
|
|
125
|
+
|
|
126
|
+
<span id="e1018"></span>
|
|
127
|
+
|
|
128
|
+
A `versionedFiles` path is absolute, or climbs out of the repository root with `..`. FerrFlow only reads and writes version files inside the repository, so write the path relative to the repository root.
|
|
129
|
+
|
|
130
|
+
### E1019: Include pattern matched no file
|
|
131
|
+
|
|
132
|
+
<span id="e1019"></span>
|
|
133
|
+
|
|
134
|
+
An entry under `include` matched no file. Patterns resolve relative to the directory of the root config file. Fix the path or remove the pattern.
|
|
135
|
+
|
|
136
|
+
### E1020: Invalid included file
|
|
137
|
+
|
|
138
|
+
<span id="e1020"></span>
|
|
139
|
+
|
|
140
|
+
A file pulled in through `include` is not a valid package description. It either declares `workspace`, `include` or `package`, which only belong in the root config, or its content does not deserialize as a package. An included file describes one package, with the same keys as a `package` entry.
|
|
141
|
+
|
|
142
|
+
### E1021: Included package outside the repository
|
|
143
|
+
|
|
144
|
+
<span id="e1021"></span>
|
|
145
|
+
|
|
146
|
+
The `path` of an included package resolves outside the repository root. In an included file, `path` is relative to that file's directory, and defaults to it when empty.
|
|
147
|
+
|
|
148
|
+
### E1022: Duplicate package name
|
|
149
|
+
|
|
150
|
+
<span id="e1022"></span>
|
|
151
|
+
|
|
152
|
+
Two packages share the same `name`, whether they come from the root config or from `include`. The error names both paths. Rename one of them.
|
|
153
|
+
|
|
154
|
+
### E1023: Package has no path
|
|
155
|
+
|
|
156
|
+
<span id="e1023"></span>
|
|
157
|
+
|
|
158
|
+
A package in the root config has no `path`. Set it relative to the repository root, or move the package into its own file listed under `include`, where `path` defaults to that file's directory.
|
|
159
|
+
|
|
124
160
|
### E1024: Versioned file does not exist
|
|
125
161
|
|
|
126
162
|
<span id="e1024"></span>
|
|
@@ -268,6 +304,39 @@ After pushing, the release commit could not be verified on the remote branch.
|
|
|
268
304
|
|
|
269
305
|
The remote branch was not found after a push operation.
|
|
270
306
|
|
|
307
|
+
### E2011: Release already running
|
|
308
|
+
|
|
309
|
+
<span id="e2011"></span>
|
|
310
|
+
|
|
311
|
+
Another `ferrflow release` holds the release lock at `.git/ferrflow.lock`, or the lockfile could not be created. A lock left by a dead process on the same machine is taken over automatically, and a lock from another machine once it is more than six hours old. The message prints the lock's content so you can see who owns it.
|
|
312
|
+
|
|
313
|
+
<aside class="ferr-aside ferr-aside--tip"><div class="ferr-aside__body"><p>If no other release is running, delete the lockfile or rerun with <code>--force-unlock</code>.</p>
|
|
314
|
+
</div></aside>
|
|
315
|
+
|
|
316
|
+
### E2012: Failed to force-push release branch
|
|
317
|
+
|
|
318
|
+
<span id="e2012"></span>
|
|
319
|
+
|
|
320
|
+
FerrFlow could not force-push the branch behind the release PR or MR. The message includes git's output. Check that the token can push to that branch and that no protection rule forbids force pushes on it.
|
|
321
|
+
|
|
322
|
+
### E2013: Cannot inspect release branch
|
|
323
|
+
|
|
324
|
+
<span id="e2013"></span>
|
|
325
|
+
|
|
326
|
+
Before reusing the release branch, FerrFlow runs `git ls-remote`, `git fetch` and `git log` on it to check that it only holds commits FerrFlow authored. One of those commands failed. The release does not stop: FerrFlow prints a warning and goes on as if the branch held only its own commits.
|
|
327
|
+
|
|
328
|
+
### E2014: Failed to delete remote tag
|
|
329
|
+
|
|
330
|
+
<span id="e2014"></span>
|
|
331
|
+
|
|
332
|
+
`ferrflow rollback` could not delete, with `git push --delete`, a tag the failed run had pushed. A tag the remote no longer has, or that now points at another commit, is skipped instead. Check that the token can delete tags, then rerun the rollback.
|
|
333
|
+
|
|
334
|
+
### E2015: Revert failed
|
|
335
|
+
|
|
336
|
+
<span id="e2015"></span>
|
|
337
|
+
|
|
338
|
+
`ferrflow rollback` could not `git revert` the release commit, for example because it conflicts with later changes. Finish the revert by hand. FerrFlow never pushes the revert: push the branch yourself once you have checked it.
|
|
339
|
+
|
|
271
340
|
### E2016: Shadow clone failed
|
|
272
341
|
|
|
273
342
|
<span id="e2016"></span>
|
|
@@ -339,6 +408,42 @@ The GitHub GraphQL API returned an unexpected response.
|
|
|
339
408
|
|
|
340
409
|
The GraphQL mutation to enable auto-merge returned an error.
|
|
341
410
|
|
|
411
|
+
### E3011: Failed to look up release PR
|
|
412
|
+
|
|
413
|
+
<span id="e3011"></span>
|
|
414
|
+
|
|
415
|
+
Listing open pull requests failed while FerrFlow looked for an existing release PR to update. Check the token and that the GitHub API is reachable.
|
|
416
|
+
|
|
417
|
+
### E3012: Failed to update release PR
|
|
418
|
+
|
|
419
|
+
<span id="e3012"></span>
|
|
420
|
+
|
|
421
|
+
FerrFlow found the open release PR, but GitHub rejected the update to its title and body. Check that the token has `pull-requests: write`.
|
|
422
|
+
|
|
423
|
+
### E3013: GraphQL request failed
|
|
424
|
+
|
|
425
|
+
<span id="e3013"></span>
|
|
426
|
+
|
|
427
|
+
A request to the GitHub GraphQL API failed before a usable response came back, either on the network or with an HTTP error status. FerrFlow calls this API to author the release commit with `createCommitOnBranch` when `FERRFLOW_BOT` is set.
|
|
428
|
+
|
|
429
|
+
### E3014: GraphQL error
|
|
430
|
+
|
|
431
|
+
<span id="e3014"></span>
|
|
432
|
+
|
|
433
|
+
The GitHub GraphQL API answered with an error, or `createCommitOnBranch` returned no commit id. The message carries GitHub's error text.
|
|
434
|
+
|
|
435
|
+
### E3015: Failed to move release branch
|
|
436
|
+
|
|
437
|
+
<span id="e3015"></span>
|
|
438
|
+
|
|
439
|
+
With `FERRFLOW_BOT` set, FerrFlow points the release branch at the head of the target branch through the GitHub refs API before committing onto it. GitHub rejected the update, or the creation of the ref when the branch did not exist yet. Check that the token has `contents: write`.
|
|
440
|
+
|
|
441
|
+
### E3016: Failed to delete release
|
|
442
|
+
|
|
443
|
+
<span id="e3016"></span>
|
|
444
|
+
|
|
445
|
+
`ferrflow rollback` could not delete a GitHub release the failed run had created. Delete it by hand and rerun the rollback.
|
|
446
|
+
|
|
342
447
|
## GitLab API Errors
|
|
343
448
|
|
|
344
449
|
### E3101: Failed to create release
|
|
@@ -374,82 +479,441 @@ The GitLab MR response was missing the `iid` field.
|
|
|
374
479
|
|
|
375
480
|
Could not merge the release MR via the GitLab API.
|
|
376
481
|
|
|
482
|
+
### E3106: Failed to look up release MR
|
|
483
|
+
|
|
484
|
+
<span id="e3106"></span>
|
|
485
|
+
|
|
486
|
+
Listing open merge requests failed while FerrFlow looked for an existing release MR to update. Check the token and that the GitLab API is reachable.
|
|
487
|
+
|
|
488
|
+
### E3107: Failed to update release MR
|
|
489
|
+
|
|
490
|
+
<span id="e3107"></span>
|
|
491
|
+
|
|
492
|
+
FerrFlow found the open release MR, but GitLab rejected the update to its title and description. Check the token's permissions on the project.
|
|
493
|
+
|
|
494
|
+
## Gitea API Errors
|
|
495
|
+
|
|
496
|
+
### E3201: Failed to create release
|
|
497
|
+
|
|
498
|
+
<span id="e3201"></span>
|
|
499
|
+
|
|
500
|
+
The Gitea Releases API returned an error when creating a release. Check that the token can write to the repository.
|
|
501
|
+
|
|
502
|
+
### E3202: Failed to list releases
|
|
503
|
+
|
|
504
|
+
<span id="e3202"></span>
|
|
505
|
+
|
|
506
|
+
Could not list releases from the Gitea API while looking for an existing draft release for the tag.
|
|
507
|
+
|
|
508
|
+
### E3203: Failed to publish release
|
|
509
|
+
|
|
510
|
+
<span id="e3203"></span>
|
|
511
|
+
|
|
512
|
+
Could not publish (un-draft) a Gitea release.
|
|
513
|
+
|
|
514
|
+
## Bitbucket API Errors
|
|
515
|
+
|
|
516
|
+
### E3301: Failed to resolve release tag
|
|
517
|
+
|
|
518
|
+
<span id="e3301"></span>
|
|
519
|
+
|
|
520
|
+
Bitbucket has no releases. On Bitbucket Cloud, FerrFlow looks the new tag up through the API instead, to link to it, and that request failed. Check that the token can read the repository and that the tag was pushed.
|
|
521
|
+
|
|
377
522
|
## Version File Errors
|
|
378
523
|
|
|
379
|
-
|
|
380
|
-
|
|
381
|
-
|
|
382
|
-
|
|
383
|
-
|
|
384
|
-
|
|
385
|
-
|
|
386
|
-
|
|
387
|
-
|
|
388
|
-
|
|
389
|
-
|
|
390
|
-
|
|
391
|
-
|
|
392
|
-
|
|
393
|
-
|
|
394
|
-
|
|
395
|
-
|
|
396
|
-
|
|
397
|
-
|
|
398
|
-
|
|
399
|
-
###
|
|
400
|
-
|
|
401
|
-
|
|
402
|
-
|
|
403
|
-
|
|
404
|
-
|
|
405
|
-
|
|
406
|
-
|
|
407
|
-
|
|
408
|
-
|
|
409
|
-
|
|
410
|
-
|
|
411
|
-
|
|
412
|
-
|
|
413
|
-
|
|
414
|
-
|
|
415
|
-
|
|
416
|
-
|
|
417
|
-
###
|
|
418
|
-
|
|
419
|
-
|
|
420
|
-
|
|
421
|
-
|
|
422
|
-
|
|
423
|
-
|
|
424
|
-
|
|
425
|
-
|
|
426
|
-
|
|
427
|
-
|
|
428
|
-
|
|
429
|
-
|
|
430
|
-
|
|
431
|
-
|
|
432
|
-
|
|
433
|
-
|
|
434
|
-
|
|
435
|
-
###
|
|
436
|
-
|
|
437
|
-
|
|
438
|
-
|
|
439
|
-
|
|
440
|
-
|
|
441
|
-
|
|
442
|
-
|
|
443
|
-
|
|
444
|
-
|
|
445
|
-
|
|
446
|
-
|
|
447
|
-
|
|
448
|
-
|
|
449
|
-
|
|
450
|
-
|
|
451
|
-
|
|
452
|
-
|
|
524
|
+
Each format has its own range of codes. The invalid UTF-8 codes come from `ferrflow validate`, which reads versioned files as raw bytes; every other command reports a file that is not UTF-8 under the format's read error.
|
|
525
|
+
|
|
526
|
+
### E4101: Cannot read TOML file
|
|
527
|
+
|
|
528
|
+
<span id="e4101"></span>
|
|
529
|
+
|
|
530
|
+
FerrFlow could not read the TOML version file (`Cargo.toml`, `pyproject.toml`) from disk.
|
|
531
|
+
|
|
532
|
+
### E4102: Invalid TOML syntax
|
|
533
|
+
|
|
534
|
+
<span id="e4102"></span>
|
|
535
|
+
|
|
536
|
+
The TOML version file does not parse. The message gives the position of the error.
|
|
537
|
+
|
|
538
|
+
### E4103: No version found in TOML file
|
|
539
|
+
|
|
540
|
+
<span id="e4103"></span>
|
|
541
|
+
|
|
542
|
+
None of `package.version`, `workspace.package.version`, `project.version` or `tool.poetry.version` is set. A `Cargo.toml` with `version.workspace = true` also lands here when the same file has no `[workspace.package].version`: point the versioned file at the workspace root `Cargo.toml` instead.
|
|
543
|
+
|
|
544
|
+
### E4104: Cannot write TOML file
|
|
545
|
+
|
|
546
|
+
<span id="e4104"></span>
|
|
547
|
+
|
|
548
|
+
Writing the new version back to the TOML version file (`Cargo.toml`, `pyproject.toml`) failed.
|
|
549
|
+
|
|
550
|
+
### E4105: Invalid UTF-8 in TOML file
|
|
551
|
+
|
|
552
|
+
<span id="e4105"></span>
|
|
553
|
+
|
|
554
|
+
The content of the TOML version file (`Cargo.toml`, `pyproject.toml`) is not valid UTF-8.
|
|
555
|
+
|
|
556
|
+
### E4201: Cannot read JSON file
|
|
557
|
+
|
|
558
|
+
<span id="e4201"></span>
|
|
559
|
+
|
|
560
|
+
FerrFlow could not read the JSON version file (`package.json`, `composer.json`) from disk. The same code covers the release checkpoint `.git/ferrflow.checkpoint.json`.
|
|
561
|
+
|
|
562
|
+
### E4202: Invalid JSON syntax
|
|
563
|
+
|
|
564
|
+
<span id="e4202"></span>
|
|
565
|
+
|
|
566
|
+
The JSON version file does not parse. FerrFlow also raises this code when the release checkpoint `.git/ferrflow.checkpoint.json` is corrupt or was written by another FerrFlow version: delete that file to start fresh.
|
|
567
|
+
|
|
568
|
+
### E4203: No version found in JSON file
|
|
569
|
+
|
|
570
|
+
<span id="e4203"></span>
|
|
571
|
+
|
|
572
|
+
The JSON file has no top-level `version` field.
|
|
573
|
+
|
|
574
|
+
### E4204: Cannot write JSON file
|
|
575
|
+
|
|
576
|
+
<span id="e4204"></span>
|
|
577
|
+
|
|
578
|
+
Writing the new version back to the JSON version file (`package.json`, `composer.json`) failed. FerrFlow also raises it when it cannot save or delete the release checkpoint, or cannot rewrite a dependent package's manifest (`package.json` or `Cargo.toml`) to point at a bumped dependency.
|
|
579
|
+
|
|
580
|
+
### E4205: Invalid UTF-8 in JSON file
|
|
581
|
+
|
|
582
|
+
<span id="e4205"></span>
|
|
583
|
+
|
|
584
|
+
The content of the JSON version file (`package.json`, `composer.json`) is not valid UTF-8.
|
|
585
|
+
|
|
586
|
+
### E4301: Cannot read Chart.yaml (helm)
|
|
587
|
+
|
|
588
|
+
<span id="e4301"></span>
|
|
589
|
+
|
|
590
|
+
FerrFlow could not read the `Chart.yaml` declared with `format = "helm"` from disk.
|
|
591
|
+
|
|
592
|
+
### E4302: No version found in Chart.yaml (helm)
|
|
593
|
+
|
|
594
|
+
<span id="e4302"></span>
|
|
595
|
+
|
|
596
|
+
The `Chart.yaml` declared with `format = "helm"` has no top-level `version:` field.
|
|
597
|
+
|
|
598
|
+
### E4303: Cannot write Chart.yaml (helm)
|
|
599
|
+
|
|
600
|
+
<span id="e4303"></span>
|
|
601
|
+
|
|
602
|
+
Writing the new version back to the `Chart.yaml` declared with `format = "helm"` failed.
|
|
603
|
+
|
|
604
|
+
### E4304: Invalid UTF-8 in Chart.yaml (helm)
|
|
605
|
+
|
|
606
|
+
<span id="e4304"></span>
|
|
607
|
+
|
|
608
|
+
The content of the `Chart.yaml` declared with `format = "helm"` is not valid UTF-8.
|
|
609
|
+
|
|
610
|
+
### E4401: Cannot read XML file
|
|
611
|
+
|
|
612
|
+
<span id="e4401"></span>
|
|
613
|
+
|
|
614
|
+
FerrFlow could not read the XML version file (`pom.xml`) from disk.
|
|
615
|
+
|
|
616
|
+
### E4402: No version found in XML file
|
|
617
|
+
|
|
618
|
+
<span id="e4402"></span>
|
|
619
|
+
|
|
620
|
+
The XML file has no `<version>` tag.
|
|
621
|
+
|
|
622
|
+
### E4403: Cannot write XML file
|
|
623
|
+
|
|
624
|
+
<span id="e4403"></span>
|
|
625
|
+
|
|
626
|
+
Writing the new version back to the XML version file (`pom.xml`) failed.
|
|
627
|
+
|
|
628
|
+
### E4404: Invalid UTF-8 in XML file
|
|
629
|
+
|
|
630
|
+
<span id="e4404"></span>
|
|
631
|
+
|
|
632
|
+
The content of the XML version file (`pom.xml`) is not valid UTF-8.
|
|
633
|
+
|
|
634
|
+
### E4410: Cannot read .csproj file
|
|
635
|
+
|
|
636
|
+
<span id="e4410"></span>
|
|
637
|
+
|
|
638
|
+
FerrFlow could not read the `.csproj` file from disk.
|
|
639
|
+
|
|
640
|
+
### E4411: No version found in .csproj file
|
|
641
|
+
|
|
642
|
+
<span id="e4411"></span>
|
|
643
|
+
|
|
644
|
+
The `.csproj` file has no `<Version>` element.
|
|
645
|
+
|
|
646
|
+
### E4412: Cannot write .csproj file
|
|
647
|
+
|
|
648
|
+
<span id="e4412"></span>
|
|
649
|
+
|
|
650
|
+
Writing the new version back to the `.csproj` file failed.
|
|
651
|
+
|
|
652
|
+
### E4413: Invalid UTF-8 in .csproj file
|
|
653
|
+
|
|
654
|
+
<span id="e4413"></span>
|
|
655
|
+
|
|
656
|
+
The content of the `.csproj` file is not valid UTF-8.
|
|
657
|
+
|
|
658
|
+
### E4501: Cannot read Gradle file
|
|
659
|
+
|
|
660
|
+
<span id="e4501"></span>
|
|
661
|
+
|
|
662
|
+
FerrFlow could not read the Gradle build file (`build.gradle`, `build.gradle.kts`) from disk.
|
|
663
|
+
|
|
664
|
+
### E4502: No version found in Gradle file
|
|
665
|
+
|
|
666
|
+
<span id="e4502"></span>
|
|
667
|
+
|
|
668
|
+
The Gradle build file has no `version = "…"` assignment.
|
|
669
|
+
|
|
670
|
+
### E4503: Cannot write Gradle file
|
|
671
|
+
|
|
672
|
+
<span id="e4503"></span>
|
|
673
|
+
|
|
674
|
+
Writing the new version back to the Gradle build file (`build.gradle`, `build.gradle.kts`) failed.
|
|
675
|
+
|
|
676
|
+
### E4504: Invalid UTF-8 in Gradle file
|
|
677
|
+
|
|
678
|
+
<span id="e4504"></span>
|
|
679
|
+
|
|
680
|
+
The content of the Gradle build file (`build.gradle`, `build.gradle.kts`) is not valid UTF-8.
|
|
681
|
+
|
|
682
|
+
### E4601: Failed to run git describe
|
|
683
|
+
|
|
684
|
+
<span id="e4601"></span>
|
|
685
|
+
|
|
686
|
+
A `gomod` versioned file takes its version from git tags through `git describe`, and the command could not be started. Check that git is on the `PATH`.
|
|
687
|
+
|
|
688
|
+
### E4602: No version tag found
|
|
689
|
+
|
|
690
|
+
<span id="e4602"></span>
|
|
691
|
+
|
|
692
|
+
`git describe` found no tag matching `*@v*` or `v*` for the package.
|
|
693
|
+
|
|
694
|
+
Starting with FerrFlow v3 the release flow catches this case and falls back to the strategy's bootstrap baseline (`0.0.0` / `0` / …), so the first release on a brand-new repo succeeds without a pre-seeded tag. The error code still exists for programs that import `GoModVersionFile` directly, but end users running `ferrflow release` should not see it anymore.
|
|
695
|
+
|
|
696
|
+
### E4603: Cannot read a version from go.mod
|
|
697
|
+
|
|
698
|
+
<span id="e4603"></span>
|
|
699
|
+
|
|
700
|
+
The version of a Go module comes from git tags, so FerrFlow cannot read one from the content of `go.mod`. `ferrflow validate` skips `gomod` entries with a warning instead.
|
|
701
|
+
|
|
702
|
+
### E4701: Cannot read text file
|
|
703
|
+
|
|
704
|
+
<span id="e4701"></span>
|
|
705
|
+
|
|
706
|
+
FerrFlow could not read the text version file (`VERSION`, `VERSION.txt`) from disk.
|
|
707
|
+
|
|
708
|
+
### E4702: No version found in text file
|
|
709
|
+
|
|
710
|
+
<span id="e4702"></span>
|
|
711
|
+
|
|
712
|
+
The text file is empty. With a `selector`, this code also covers a regex that does not compile, does not have exactly one capture group, matches nothing or captures only whitespace.
|
|
713
|
+
|
|
714
|
+
### E4703: Cannot write text file
|
|
715
|
+
|
|
716
|
+
<span id="e4703"></span>
|
|
717
|
+
|
|
718
|
+
Writing the new version back to the text version file (`VERSION`, `VERSION.txt`) failed.
|
|
719
|
+
|
|
720
|
+
### E4704: Invalid UTF-8 in text file
|
|
721
|
+
|
|
722
|
+
<span id="e4704"></span>
|
|
723
|
+
|
|
724
|
+
The content of the text version file (`VERSION`, `VERSION.txt`) is not valid UTF-8.
|
|
725
|
+
|
|
726
|
+
### E4801: Cannot read pubspec.yaml
|
|
727
|
+
|
|
728
|
+
<span id="e4801"></span>
|
|
729
|
+
|
|
730
|
+
FerrFlow could not read `pubspec.yaml` from disk.
|
|
731
|
+
|
|
732
|
+
### E4802: No version found in pubspec.yaml
|
|
733
|
+
|
|
734
|
+
<span id="e4802"></span>
|
|
735
|
+
|
|
736
|
+
`pubspec.yaml` has no top-level `version:` key.
|
|
737
|
+
|
|
738
|
+
### E4803: Cannot write pubspec.yaml
|
|
739
|
+
|
|
740
|
+
<span id="e4803"></span>
|
|
741
|
+
|
|
742
|
+
Writing the new version back to `pubspec.yaml` failed.
|
|
743
|
+
|
|
744
|
+
### E4804: Invalid UTF-8 in pubspec.yaml
|
|
745
|
+
|
|
746
|
+
<span id="e4804"></span>
|
|
747
|
+
|
|
748
|
+
The content of `pubspec.yaml` is not valid UTF-8.
|
|
749
|
+
|
|
750
|
+
### E4811: Cannot read mix.exs
|
|
751
|
+
|
|
752
|
+
<span id="e4811"></span>
|
|
753
|
+
|
|
754
|
+
FerrFlow could not read `mix.exs` from disk.
|
|
755
|
+
|
|
756
|
+
### E4812: No version found in mix.exs
|
|
757
|
+
|
|
758
|
+
<span id="e4812"></span>
|
|
759
|
+
|
|
760
|
+
`mix.exs` has no `version: "…"` literal.
|
|
761
|
+
|
|
762
|
+
### E4813: Cannot write mix.exs
|
|
763
|
+
|
|
764
|
+
<span id="e4813"></span>
|
|
765
|
+
|
|
766
|
+
Writing the new version back to `mix.exs` failed.
|
|
767
|
+
|
|
768
|
+
### E4814: Invalid UTF-8 in mix.exs
|
|
769
|
+
|
|
770
|
+
<span id="e4814"></span>
|
|
771
|
+
|
|
772
|
+
The content of `mix.exs` is not valid UTF-8.
|
|
773
|
+
|
|
774
|
+
### E4821: Cannot read Chart.yaml (chartyaml)
|
|
775
|
+
|
|
776
|
+
<span id="e4821"></span>
|
|
777
|
+
|
|
778
|
+
FerrFlow could not read the `Chart.yaml` declared with `format = "chartyaml"` from disk.
|
|
779
|
+
|
|
780
|
+
### E4822: No version found in Chart.yaml (chartyaml)
|
|
781
|
+
|
|
782
|
+
<span id="e4822"></span>
|
|
783
|
+
|
|
784
|
+
The `Chart.yaml` declared with `format = "chartyaml"` has no top-level `version:` key.
|
|
785
|
+
|
|
786
|
+
### E4823: Cannot write Chart.yaml (chartyaml)
|
|
787
|
+
|
|
788
|
+
<span id="e4823"></span>
|
|
789
|
+
|
|
790
|
+
Writing the new version back to the `Chart.yaml` declared with `format = "chartyaml"` failed.
|
|
791
|
+
|
|
792
|
+
### E4824: Invalid UTF-8 in Chart.yaml (chartyaml)
|
|
793
|
+
|
|
794
|
+
<span id="e4824"></span>
|
|
795
|
+
|
|
796
|
+
The content of the `Chart.yaml` declared with `format = "chartyaml"` is not valid UTF-8.
|
|
797
|
+
|
|
798
|
+
### E4831: Cannot read gemspec
|
|
799
|
+
|
|
800
|
+
<span id="e4831"></span>
|
|
801
|
+
|
|
802
|
+
FerrFlow could not read the `.gemspec` file from disk.
|
|
803
|
+
|
|
804
|
+
### E4832: No version found in gemspec
|
|
805
|
+
|
|
806
|
+
<span id="e4832"></span>
|
|
807
|
+
|
|
808
|
+
The `.gemspec` file has no `<ident>.version = "…"` assignment.
|
|
809
|
+
|
|
810
|
+
### E4833: Cannot write gemspec
|
|
811
|
+
|
|
812
|
+
<span id="e4833"></span>
|
|
813
|
+
|
|
814
|
+
Writing the new version back to the `.gemspec` file failed.
|
|
815
|
+
|
|
816
|
+
### E4834: Invalid UTF-8 in gemspec
|
|
817
|
+
|
|
818
|
+
<span id="e4834"></span>
|
|
819
|
+
|
|
820
|
+
The content of the `.gemspec` file is not valid UTF-8.
|
|
821
|
+
|
|
822
|
+
### E4841: Cannot read Package.swift
|
|
823
|
+
|
|
824
|
+
<span id="e4841"></span>
|
|
825
|
+
|
|
826
|
+
FerrFlow could not read `Package.swift` from disk.
|
|
827
|
+
|
|
828
|
+
### E4842: No version found in Package.swift
|
|
829
|
+
|
|
830
|
+
<span id="e4842"></span>
|
|
831
|
+
|
|
832
|
+
`Package.swift` has no top-level `let <name>Version = "…"` declaration.
|
|
833
|
+
|
|
834
|
+
### E4843: Cannot write Package.swift
|
|
835
|
+
|
|
836
|
+
<span id="e4843"></span>
|
|
837
|
+
|
|
838
|
+
Writing the new version back to `Package.swift` failed.
|
|
839
|
+
|
|
840
|
+
### E4844: Invalid UTF-8 in Package.swift
|
|
841
|
+
|
|
842
|
+
<span id="e4844"></span>
|
|
843
|
+
|
|
844
|
+
The content of `Package.swift` is not valid UTF-8.
|
|
845
|
+
|
|
846
|
+
### E4851: Cannot read .cabal file
|
|
847
|
+
|
|
848
|
+
<span id="e4851"></span>
|
|
849
|
+
|
|
850
|
+
FerrFlow could not read the `.cabal` file from disk.
|
|
851
|
+
|
|
852
|
+
### E4852: No version found in .cabal file
|
|
853
|
+
|
|
854
|
+
<span id="e4852"></span>
|
|
855
|
+
|
|
856
|
+
The `.cabal` file has no top-level `version:` field.
|
|
857
|
+
|
|
858
|
+
### E4853: Cannot write .cabal file
|
|
859
|
+
|
|
860
|
+
<span id="e4853"></span>
|
|
861
|
+
|
|
862
|
+
Writing the new version back to the `.cabal` file failed.
|
|
863
|
+
|
|
864
|
+
### E4854: Invalid UTF-8 in .cabal file
|
|
865
|
+
|
|
866
|
+
<span id="e4854"></span>
|
|
867
|
+
|
|
868
|
+
The content of the `.cabal` file is not valid UTF-8.
|
|
869
|
+
|
|
870
|
+
### E4861: Cannot read CMakeLists.txt
|
|
871
|
+
|
|
872
|
+
<span id="e4861"></span>
|
|
873
|
+
|
|
874
|
+
FerrFlow could not read `CMakeLists.txt` from disk.
|
|
875
|
+
|
|
876
|
+
### E4862: No version found in CMakeLists.txt
|
|
877
|
+
|
|
878
|
+
<span id="e4862"></span>
|
|
879
|
+
|
|
880
|
+
`CMakeLists.txt` has no `project(… VERSION …)` declaration.
|
|
881
|
+
|
|
882
|
+
### E4863: Cannot write CMakeLists.txt
|
|
883
|
+
|
|
884
|
+
<span id="e4863"></span>
|
|
885
|
+
|
|
886
|
+
Writing the new version back to `CMakeLists.txt` failed.
|
|
887
|
+
|
|
888
|
+
### E4864: Invalid UTF-8 in CMakeLists.txt
|
|
889
|
+
|
|
890
|
+
<span id="e4864"></span>
|
|
891
|
+
|
|
892
|
+
The content of `CMakeLists.txt` is not valid UTF-8.
|
|
893
|
+
|
|
894
|
+
### E4871: Cannot read galaxy.yml
|
|
895
|
+
|
|
896
|
+
<span id="e4871"></span>
|
|
897
|
+
|
|
898
|
+
FerrFlow could not read `galaxy.yml` from disk.
|
|
899
|
+
|
|
900
|
+
### E4872: No version found in galaxy.yml
|
|
901
|
+
|
|
902
|
+
<span id="e4872"></span>
|
|
903
|
+
|
|
904
|
+
`galaxy.yml` has no top-level `version:` key.
|
|
905
|
+
|
|
906
|
+
### E4873: Cannot write galaxy.yml
|
|
907
|
+
|
|
908
|
+
<span id="e4873"></span>
|
|
909
|
+
|
|
910
|
+
Writing the new version back to `galaxy.yml` failed.
|
|
911
|
+
|
|
912
|
+
### E4874: Invalid UTF-8 in galaxy.yml
|
|
913
|
+
|
|
914
|
+
<span id="e4874"></span>
|
|
915
|
+
|
|
916
|
+
The content of `galaxy.yml` is not valid UTF-8.
|
|
453
917
|
|
|
454
918
|
## Pre-release Errors
|
|
455
919
|
|
|
@@ -490,6 +954,23 @@ A lifecycle hook exited with a non-zero status code and `on_failure` is set to `
|
|
|
490
954
|
<aside class="ferr-aside ferr-aside--tip"><div class="ferr-aside__body"><p>Check the hook command output, or set <code>on_failure: "continue"</code> to ignore failures.</p>
|
|
491
955
|
</div></aside>
|
|
492
956
|
|
|
957
|
+
## Publisher Errors
|
|
958
|
+
|
|
959
|
+
### E6101: Publisher misconfigured
|
|
960
|
+
|
|
961
|
+
<span id="e6101"></span>
|
|
962
|
+
|
|
963
|
+
A publisher could not start because its setup is incomplete: a `registry` that is not declared under `workspace.registries`, a `tokenEnv` variable that is not set, a build context, chart or asset file that does not exist, or a `trustedPublishing` setup outside GitHub Actions. The message names the publisher and the missing piece. Nothing was published.
|
|
964
|
+
|
|
965
|
+
### E6102: Publish failed
|
|
966
|
+
|
|
967
|
+
<span id="e6102"></span>
|
|
968
|
+
|
|
969
|
+
The publish step ran and failed: `cargo publish`, `npm publish`, `twine upload`, `docker buildx`, `helm push`, `gh release upload` or a webhook returned an error. The message carries the tool's own error, including the lines that explain its cause. For cargo, FerrFlow retries a few times when the error looks like registry index lag after a dependency was just published, and reports E6102 once the retries are spent.
|
|
970
|
+
|
|
971
|
+
<aside class="ferr-aside ferr-aside--tip"><div class="ferr-aside__body"><p>Run the same command by hand from the package directory, for example <code>cargo publish --dry-run</code>, to see the full output.</p>
|
|
972
|
+
</div></aside>
|
|
973
|
+
|
|
493
974
|
## Query Errors
|
|
494
975
|
|
|
495
976
|
### E7001: No packages configured
|
|
@@ -510,6 +991,24 @@ The specified package name does not exist in the config.
|
|
|
510
991
|
<aside class="ferr-aside ferr-aside--tip"><div class="ferr-aside__body"><p>Run <code>ferrflow version</code> to list all configured packages.</p>
|
|
511
992
|
</div></aside>
|
|
512
993
|
|
|
994
|
+
### E7003: Invalid diff range
|
|
995
|
+
|
|
996
|
+
<span id="e7003"></span>
|
|
997
|
+
|
|
998
|
+
`ferrflow diff` needs a range written `<from>..<to>`, with both sides non-empty, for example `v1.4.0..v1.6.0`.
|
|
999
|
+
|
|
1000
|
+
### E7004: Package name required
|
|
1001
|
+
|
|
1002
|
+
<span id="e7004"></span>
|
|
1003
|
+
|
|
1004
|
+
The repository is a monorepo, so `ferrflow diff` needs to know which package to compare: `ferrflow diff <package> <from>..<to>`.
|
|
1005
|
+
|
|
1006
|
+
### E7005: Range endpoint not found
|
|
1007
|
+
|
|
1008
|
+
<span id="e7005"></span>
|
|
1009
|
+
|
|
1010
|
+
One side of the `ferrflow diff` range does not resolve to a tag. FerrFlow tries the value as given, then as a version rendered with the package's tag template, with and without a leading `v`. The message lists the names it tried. Pass an existing tag name or version.
|
|
1011
|
+
|
|
513
1012
|
## Monorepo Errors
|
|
514
1013
|
|
|
515
1014
|
### E8001: Package not found in config
|
|
@@ -532,3 +1031,11 @@ A floating tag would move to an older version.
|
|
|
532
1031
|
<span id="e8003"></span>
|
|
533
1032
|
|
|
534
1033
|
Two or more packages depend on each other through `dependsOn`, directly or transitively, so there is no order in which to release them. The message names the loop, e.g. `cycle detected: api → web → api`. Remove one of the `dependsOn` edges to break it. The check runs before any version is written, so a cyclic configuration never leaves a partial release behind.
|
|
1034
|
+
|
|
1035
|
+
## Rollback Errors
|
|
1036
|
+
|
|
1037
|
+
### E10000: Rollback blocked
|
|
1038
|
+
|
|
1039
|
+
<span id="e10000"></span>
|
|
1040
|
+
|
|
1041
|
+
Every package in the failed run published to a registry that cannot be unpublished, so `ferrflow rollback` has nothing it can undo. The plan it prints names each blocked package and the reason.
|