crystal
/
forgejo
forked from forgejo/forgejo
1
0
Fork 0
Code Issues Pull Requests Activity

[crystal/release] Forgejo v1.18.3-2crystal0 #2

New Issue
Closed
opened 2023-02-18 16:12:35 -07:00 by crystal · 1 comment
crystal commented 2023-02-18 16:12:35 -07:00
Owner

A new version of Forgejo was released yesterday. I have uncharacteristically upgraded CrystalCommit Forge to the new release instead of rushing out an update to my fork as usual. I opted to do this for two reasons:

  • The previous release of my fork inherited a bug from upstream Forgejo which would have made preparing this release more difficult. This bug was fixed in yesterday's release, and will be included in this release of my fork.
  • I was responsible for a large portion of the prepwork on Forgejo's official release yesterday. After publishing the release, I took a brief break from working on Forgejo to preserve my sanity.
A new version of Forgejo was released yesterday. I have uncharacteristically upgraded CrystalCommit Forge to the new release instead of rushing out an update to my fork as usual. I opted to do this for two reasons: - The previous release of my fork inherited a bug from upstream Forgejo which would have made preparing this release more difficult. This bug was fixed in yesterday's release, and will be included in this release of my fork. - [I was responsible](https://codeberg.org/forgejo/forgejo/issues/368) for a large portion of the prepwork on Forgejo's official release yesterday. After publishing the release, I took a brief break from working on Forgejo to preserve my sanity. --- - [x] Rebase `v1.18/crystal` branch - [x] Synchronize `crystal:v1.18/forgejo` with `mirror:v1.18/forgejo` - [x] Archive `v1.18/crystal` branch - [x] Create new `v1.18/crystal` branch based on `v1.18/forgejo` - [x] Update default branch - [x] Cherry-pick backports and CI commits - [x] Integration tests: `v1.18/crystal` - [x] Started: [CrystalIntegration](https://ci.cryxtal.org/crystal/forgejo/build/47) - [x] Passed: compliance - [x] Passed: testing-amd64 (takes up to an hour) - [x] Update [forgejo-build](https://sc.cryxtal.org/crystal/forgejo-build) - [x] Reset submodule - [x] Push changes - [x] Test build - [x] Started: [CrystalIntegration](https://ci.cryxtal.org/crystal/forgejo-build/build/47) - `ci-verify` will not proceed until there is a passing [pipeline for the target commit](https://ci.cryxtal.org/crystal/forgejo/build/47) - [x] Passed - [x] Publish release v1.18.3-2crystal0 - [x] Create tag `v1.18.3-2crystal0` on [forgejo-build](https://sc.cryxtal.org/crystal/forgejo-build) - [x] Build started: [CrystalIntegration](https://ci.cryxtal.org/crystal/forgejo-build/build/48) - [x] Build published: [forgejo-build Releases](https://sc.cryxtal.org/crystal/forgejo-build) - [x] Add release message: [Release v1.18.3-2crystal0](https://sc.cryxtal.org/crystal/forgejo-build/releases/tag/v1.18.3-2crystal0) - [x] Deploy the new release to CrystalCommit Forge
crystal commented 2023-02-19 11:47:20 -07:00
Poster
Owner

At long last, the new build has been deployed to CrystalCommit Forge.

At long last, the new build has been deployed to CrystalCommit Forge.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
pr/releasenotes-1.21.11-0
forgejo
pr/gitea-version
test/6543-doctor
v1.20/forgejo
v1.19/crystal
v1.19/forgejo
v1.18/crystal
v1.20/crystal
pr/issue-template-next
forgejo-development
v1.18/forgejo
crystal/ssh-key-fix-test
pr/a11y-bp-fix
pr/swagger-title
archive/2023-02-24/v1.18/crystal
pr/doc-release-notes-1.18.3-2
archive/2023-02-18/v1.18/crystal
crystal/ci-bp-merge
crystal/ci
archive/2023-02-09/v1.18/crystal
main
release/v1.18
v1.19.4-0
v1.19.3-0
v1.19.2-0
v1.19.1-0
v1.19.0-3
v1.19.0-2
v1.18.5-0
v1.20.0-dev
v1.18.3-2
v1.18.3-1
v1.18.3-0
v1.18.2-1
v1.18.2-0
v1.18.1-0
v1.18.0-1
v1.18.0-0
v1.18.0-rc1-2
v1.18.0-rc1-1
v1.18.0-rc1
v1.18.0-rc0
v1.19.0-dev
v1.17.3
v1.17.2
v1.17.1
v1.17.0
v1.17.0-rc2
v1.16.9
v1.17.0-rc1
v1.18.0-dev
v1.16.8
v1.16.7
v1.16.6
v1.16.5
v1.16.4
v1.16.3
v1.16.2
v1.16.1
v1.16.0
v1.15.11
v1.17.0-dev
v1.16.0-rc1
v1.15.10
v1.15.9
v1.15.8
v1.15.7
v1.15.6
v1.15.5
v1.15.4
v1.15.3
v1.15.2
v1.15.1
v1.14.7
v1.15.0
v1.15.0-rc3
v1.14.6
v1.15.0-rc2
v1.14.5
v1.16.0-dev
v1.15.0-rc1
v1.14.4
v1.14.3
v1.14.2
v1.14.1
v1.14.0
v1.13.7
v1.14.0-rc2
v1.13.6
v1.13.5
v1.14.0-rc1
v1.15.0-dev
v1.13.4
v1.13.3
v1.13.2
v1.13.1
v1.13.0
v1.12.6
v1.13.0-rc2
v1.14.0-dev
v1.13.0-rc1
v1.12.5
v1.12.4
v1.12.3
v1.12.2
v1.12.1
v1.11.8
v1.12.0
v1.11.7
v1.12.0-rc2
v1.11.6
v1.12.0-rc1
v1.13.0-dev
v1.11.5
v1.11.4
v1.11.3
v1.10.6
v1.12.0-dev
v1.11.2
v1.10.5
v1.11.1
v1.10.4
v1.11.0
v1.11.0-rc2
v1.10.3
v1.11.0-rc1
v1.10.2
v1.10.1
v1.10.0
v1.9.6
v1.9.5
v1.10.0-rc2
v1.11.0-dev
v1.10.0-rc1
v1.9.4
v1.9.3
v1.9.2
v1.9.1
v1.9.0
v1.9.0-rc2
v1.10.0-dev
v1.9.0-rc1
v1.8.3
v1.8.2
v1.8.1
v1.8.0
v1.8.0-rc3
v1.7.6
v1.8.0-rc2
v1.7.5
v1.8.0-rc1
v1.9.0-dev
v1.7.4
v1.7.3
v1.7.2
v1.7.1
v1.7.0
v1.7.0-rc3
v1.6.4
v1.7.0-rc2
v1.6.3
v1.7.0-rc1
v1.7.0-dev
v1.6.2
v1.6.1
v1.6.0
v1.6.0-rc2
v1.5.3
v1.6.0-rc1
v1.6.0-dev
v1.5.2
v1.5.1
v1.5.0
v1.5.0-rc2
v1.5.0-rc1
v1.5.0-dev
v1.4.3
v1.4.2
v1.4.1
v1.4.0
v1.4.0-rc3
v1.4.0-rc2
v1.3.3
v1.4.0-rc1
v1.3.2
v1.3.1
v1.3.0
v1.3.0-rc2
v1.3.0-rc1
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.2.0-rc3
v1.2.0-rc2
v1.1.4
v1.2.0-rc1
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.2
v1.0.1
v1.0.0
v0.9.99
Labels
Clear labels   
bug

The website is broken!   
duplicate

Duplicate issues   
feature/enhancement

New feature or enhancement   
help wanted

Need some help   
invalid/wontfix

Bad issues   
question

More information is needed   
upstream/Forgejo

Send upstream to Forgejo (and Gitea)   
upstream/Gitea

Send upstream to Gitea
No Label
bug
duplicate
feature/enhancement
help wanted
invalid/wontfix
question
upstream/Forgejo
upstream/Gitea
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: crystal/forgejo#2
There is no content yet.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?