github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-07 00:22:43 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #853] Use GoReleaser for automated releases? #410

New Issue
Closed
opened 2026-04-12 10:04:08 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-12 10:04:08 -05:00
Owner
Copy Link

Originally created by @coolaj86 on GitHub (Oct 20, 2023).
Original GitHub issue: https://github.com/ollama/ollama/issues/853

I am willing to help with this.

I don't see any .goreleaser.yaml or .github/workflows or any other sort of release automation in the repo.

Most Go projects use GoReleaser and I'm definitely not a hype man, but I'm definitely on the GoReleaser bus, and I'm familiar with the process for setting API tokens in GitHub Actions and could help do something like have a release created when a tag is pushed.

Would you be interested in anything like that?

Even if you don't fully automate it with release-on-tag, using GoReleaser can relieve some of the management burden.

It's also easy to have support for x86 and ARM macOS builds.

I have no-nonsense guide on GoReleaser here: https://webinstall.dev/goreleaser

Originally created by @coolaj86 on GitHub (Oct 20, 2023). Original GitHub issue: https://github.com/ollama/ollama/issues/853 I am willing to help with this. I don't see any `.goreleaser.yaml` or `.github/workflows` or any other sort of release automation in the repo. Most Go projects use GoReleaser and I'm definitely not a hype man, but I'm definitely on the GoReleaser bus, and I'm familiar with the process for setting API tokens in GitHub Actions and could help do something like have a release created when a tag is pushed. Would you be interested in anything like that? Even if you don't fully automate it with release-on-tag, using GoReleaser can relieve some of the management burden. It's also easy to have support for **x86 and ARM macOS builds**. I have no-nonsense guide on GoReleaser here: https://webinstall.dev/goreleaser
GiteaMirror commented 2026-04-12 10:04:10 -05:00
Author
Owner
Copy Link

@mxyng commented on GitHub (Oct 25, 2023):

The build for this project is more involved than normal goreleaser project. While it's possible to implement a goreleaser configuration and workflows, the project is changing quickly enough where that will become a hindrance.

It's a possibility for the future but I'm going to close this issue for now

<!-- gh-comment-id:1779875028 --> @mxyng commented on GitHub (Oct 25, 2023): The build for this project is more involved than normal goreleaser project. While it's possible to implement a goreleaser configuration and workflows, the project is changing quickly enough where that will become a hindrance. It's a possibility for the future but I'm going to close this issue for now
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label
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/ollama#410
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?