[GH-ISSUE #386] [Feature]: Provide non-stable docker containers #241

New issue

Closed

opened 2026-05-07 00:08:02 +02:00 by BreizhHardware · 1 comment

BreizhHardware commented

2026-05-07 00:08:02 +02:00

Owner

Originally created by @JasonSwindle on GitHub (Feb 15, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/386

Originally assigned to: @maziggy on GitHub.

Problem or Use Case

Howdy,

It would be lovely if there was a named tags for beta / rc / testing, or even a meta dev / unstable docker tag.

Proposed Solution

Provide non-stable docker tags

Alternatives Considered

No response

Feature Category

Other

Priority

Nice to have

Mockups or Examples

No response

Contribution

I would be willing to help implement this feature

Checklist

I have searched existing issues to ensure this feature hasn't already been requested

Originally created by @JasonSwindle on GitHub (Feb 15, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/386 Originally assigned to: @maziggy on GitHub. ### Problem or Use Case Howdy, It would be lovely if there was a named tags for beta / rc / testing, or even a meta `dev` / `unstable` docker tag. ### Proposed Solution Provide non-stable docker tags ### Alternatives Considered _No response_ ### Feature Category Other ### Priority Nice to have ### Mockups or Examples _No response_ ### Contribution - [ ] I would be willing to help implement this feature ### Checklist - [x] I have searched existing issues to ensure this feature hasn't already been requested

BreizhHardware

2026-05-07 00:08:02 +02:00

closed this issue
added the
wontfix
label

BreizhHardware commented

2026-05-07 00:08:03 +02:00

Author

Owner

@maziggy commented on GitHub (Feb 15, 2026):

We now have a dedicated beta testing team and are no longer going to release beta versions for the public. Sorry.

@maziggy commented on GitHub (Feb 15, 2026): We now have a dedicated beta testing team and are no longer going to release beta versions for the public. Sorry.

BreizhHardware referenced this issue

2026-05-07 00:15:17 +02:00

[PR #241] [MERGED] Fix for Information exposure through an exception #72 #976