Repository navigation
Releases
0.18.0
Added
- The assistant drafts a member's own dietary needs and I can usually, in private only (#278, ADR 0009, amended). On the Assistant page or in a direct message with Dinnerbell, never in a channel thread, a member can ask "Add vegetarian to my needs" or "Turn off pick up for me" and get a draft for each. Confirm runs what Save needs and Save on Preferences run, as the member with a member's permissions, even for an admin, and keeps their reminders as they are. Dietary needs are the household's dietary tags, the only ones Preferences lets a member pick, so the assistant refuses any other name and never makes a tag; it also refuses what Preferences would, in its words, such as a sixth need or a change while a call the member is in is voting. If the member changes either elsewhere first, Confirm says so and changes nothing. Look up my preferences now also returns the member's own needs, as tag names, with the household's dietary tags, and whether they usually cook, pick up, and order. Only that member's own go to Anthropic, only when they ask, and never anyone else's. Dietary needs can reveal health or religion, and Admin > Assistant says they're sent.
Changed
- The assistant no longer needs a feature flag (#294, ADR 0009). The
assistantflag, on in production since 0.16.0, is retired. The assistant now works whenDINNERBELL_ANTHROPIC_API_KEYis set and Assistant is on in Admin. Without the key, the assistant stays off everywhere, and the Admin switch still turns it off for the household. - The assistant matches a name you type to the right member (#277, ADR 0009 as amended). On the web's Assistant page and in Slack, you can name people as you say them, such as "hand off dinner to Theo" for a member listed as Theodore, without a mention. Every request to Anthropic now carries the household's roster: each active member's display name with their label in the conversation, such as "Member 2: Theodore". The model matches the name to a label, gives tools only labels, and asks which one you mean when a name could fit two members. Guests and deactivated members are never on the roster, and a label nobody has still gets the same refusal as a guest's, so nothing says whether a name is a guest's. Emails, Slack IDs, and everything else ADR 0009 keeps home still stay home. Dinnerbell still writes only labels into a stored conversation, but a member's own words and the assistant's replies keep any name as written until Conversation hours delete them. The roster is rebuilt for each message, so a rename shows at once, and every active member gets a label when a conversation starts. Admin > Assistant says that display names are sent, and the smallest message it prices for the cap now includes the household's roster.
Fixed
- Merging tags keeps members' and guests' own dietary needs (#298). Merging a dietary tag moved items, preferences, meal history, and the needs of guests a member brings to the other tag, but not the dietary needs a member or guest set for themselves. Those went on naming the removed tag: calls stopped holding picks to the need, Preferences stopped showing it, and the next Save needs dropped it. A merge now moves those needs too. A dietary tag now merges only into another dietary tag, as a cuisine merges only into a cuisine, so a need never ends up on a tag Preferences can't show.
- The assistant's tools no longer tell the model to send an empty string where one can't work (#283). Input of the wrong type for a name, day, or label a tool must have, such as a new guest's name or the member to hand off to, came back with "send an empty string for any"; now it says only that the field must be a string. Fields an empty string fills, such as a search or a part of a plan to keep, still say so.
Upgrade notes
- Migration 0039 rebuilds
assistant_draftso itskindaccepts drafts of a member's dietary needs and I can usually (#278), keeping every draft and its IDs. A downgrade to 0038 deletes those drafts still waiting for Confirm. - Remove
assistantfromDINNERBELL_FEATURES(#294). Dinnerbell ignores it now and logs a warning at startup until you take it out of.env. An install with the key and the Admin switch on keeps its assistant. An install with the key but without the flag now shows Admin > Assistant, with the assistant off until an admin turns it on. - Migration 0040 removes dietary needs that name no dietary tag of the member's household (#298), which tag merges before this release left behind. It can't tell which tag a lost need was merged into, and when a dietary tag added later reused the removed tag's ID, the need stays and names the new tag. So if your household ever merged dietary tags, ask members and guests to check Dietary needs on Preferences. A downgrade to 0039 changes nothing.
- The assistant starts sending members' display names (#277). In a household with the assistant on, every request sends each active member's display name with their label from the first message after the upgrade. No admin action is needed, and nothing asks first. Admin > Assistant says so; to stop it, turn the assistant off there.
Image
ghcr.io/dsmorgan/dinnerbell:0.18.0@sha256:939756d8b77fd84f68e866645947f9599a327d720298fbdab6f0921a5099a76a
0.17.0
Security
- opentelemetry-api 1.45.2 fixes CVE-2026-126360. FastAPI and Anthropic's SDK depend on the package; Dinnerbell doesn't configure OpenTelemetry. The 0.16.0 image has 1.45.1.
Changed
- A shuffle never brings back a place the call has shown, unless nothing else fits (#290). Dinnerbell now remembers every place a call has shown as a ranked proposal, and each shuffle draws only places not shown yet, so the second and third shuffles don't bring back the first draw's places. Unseen places for this meal come first, then unseen places for other meals, as the top-up does. When too few unseen places fit, the shuffle fills the rest from places shown before, those shown longest ago first, so the ones it just drew away come back last. If nothing fits at all, the shuffle is refused and not counted, as before. Votes, added picks, offers, and suggestions stay, and the hard filters, the limit of 3, and the messages don't change. It applies to Slack, the web, and the assistant's shuffle draft. A re-run or a restart starts with no places shown.
dinnerbell reset-history,discard-call, andscrub-testdelete the remembered places and count them. - The docs are shorter and match 0.16.0. Setup suggests writing the first catalog with an AI assistant from your email, local order history, or a list, pointed at
seed/catalog.schema.json. The catalog import matches cooks to members added on Admin > Members; they don't need to have signed in. Switching between a clone and the bundle now movesDINNERBELL_ANTHROPIC_API_KEY, and the pre-0.2.0 switch to the prebuilt image is gone. The README no longer lists a test instance as something you need.
Upgrade notes
- Migration 0038 adds one empty table,
shown_place, for the places each call has shown (#290). It changes no existing row. A call that shuffled before the upgrade has no record of its earlier draws, so its next shuffle leaves out only the picks on show. A downgrade to 0037 drops the table, and shuffles then leave out only the places they draw away.
Image
ghcr.io/dsmorgan/dinnerbell:0.17.0@sha256:922073694b02d37c51802b03417a91cbccfe28e5a68981018423af3ae648d472
0.16.0
Added
- The optional assistant's core, behind a flag (#17, ADR 0009). Nothing changes unless an operator sets
DINNERBELL_ANTHROPIC_API_KEYand addsassistanttoDINNERBELL_FEATURES; then Admin gains an Assistant tab. There the admin turns the assistant on, sets the household's Monthly cap ($1 to $100 a calendar month in the household's time zone, $5 by default) and Conversation hours (0 to 168, 24 by default), and sees this month's usage in total and per member. Each change is audited ashousehold.assistant_updated. Members talk to it in Slack and on the web's Assistant page (below). This release adds what they build on:- Before each request to Anthropic, Dinnerbell reserves the most the request can cost and refuses it if that would pass the cap, then settles the reservation to what the request cost, cache tokens included. At the cap, the assistant says it's unavailable until next month.
- Conversations are stored with members as "Member 1", "Member 2", and so on, and deleted once Conversation hours pass, every 5 minutes, or at once when the admin lowers the setting. No names, emails, Slack IDs, preferences, vetoes, ratings, or notes are sent.
- The assistant's one tool so far looks up catalog items by name or tag, acting as the member with a member's permissions, even for an admin.
DINNERBELL_ASSISTANT_MODELpicksclaude-sonnet-5-5(the default),claude-opus-5-5, orclaude-haiku-5-5; Dinnerbell refuses to start on a model it has no prices for.dinnerbell scrub-testturns the assistant off and deletes every conversation.
- The assistant's candidates, drafts, and Confirm, still behind the flag (#17). Four more tools, each acting as the member with a member's permissions, even for an admin:
- Find candidates, for a call that's voting: what passes ranking's filters for everyone who's in, in name order, optionally narrowed by days since eaten, cuisine, or mode. Reasons come only from variety, novelty, suggestions, the usual mode, volunteer fit, and meal fit, with members as "Member 1" and so on; never hints, favorites, or what the filters removed. Before voting, the assistant says to ask once voting opens.
- Draft a proposal of a candidate, draft an offer of a catalog item, and draft catalog items in the catalog file format. A catalog draft drops entries the catalog has already and lists them, and strips
cooksandactive. - Each draft says what Confirm does, such as join late, take the role the mode needs, or replace a scheduled call, lasts 30 minutes, and only its member can confirm it, once. Confirm runs the same service as the form, which checks everything again, so a stale draft gets the usual error and nothing changes. A catalog draft's Confirm opens the import preview, which only adds, even if a matching item appeared meanwhile.
- The tools pick the call the member names, then the conversation's, then the only open one, and ask when several are open.
- Expired drafts are deleted every 5 minutes, and
dinnerbell scrub-testanddinnerbell reset-historydelete them all. The web page and Slack have the Confirm and Cancel buttons (below).
- The assistant on the web: the Assistant page, behind the same flag (#17). With the key, the flag, and Admin's switch on, each active member and admin gets an Assistant link and a private conversation of their own; guests don't. A reply appears under the message without reloading the page, and the form works without JavaScript too. Replies show bold, italics, lists, and code, and their links aren't clickable. Each draft is a card that says what Confirm does, with Confirm and Cancel; a proposal or offer shows the service's result or its refusal on the card, and a catalog draft opens the import preview, which only adds. A draft that expired, was used, or isn't yours says so. Start over deletes the conversation and cancels its waiting drafts. At Conversation hours 0, the page says nothing is kept and shows only the latest exchange. Otherwise the link is hidden and the Assistant pages answer 404, as Admin > Assistant does.
- Confirm the assistant's drafts in Slack (#17). Each draft comes as a card after the reply, with what Confirm does, and Confirm and Cancel. In a channel thread the card shows only to the member who asked; in a direct message it's an ordinary message in the thread. Confirm runs the same service as the form, as that member, and the card then says what happened, or the service's reason it can't, such as a call that's no longer voting. A draft that's expired, used, or someone else's says so and changes nothing. A catalog draft's Confirm gives a Review the import link to the web's add-only import preview, signed for that member and good for 24 hours, as long as Dinnerbell keeps a confirmed catalog draft; nothing is saved until they select Apply there. While the assistant is off, the buttons say "The assistant is turned off." and change nothing. A word that only starts like
@here,@channel, or@everyone, such as "@hereford", now reads as written in replies, and the note that Dinnerbell sees only mentions comes once to each member whose replies there were private, and once to the thread with its first public reply. - The assistant drafts catalog items from a menu link, behind the same flag (#17). Give it a link to a restaurant's menu or a recipe, and it drafts catalog items for Confirm, which opens the import preview, as other catalog drafts do. Dinnerbell fetches the page under the same rules as every menu link (HTTPS, public addresses only, 2 MB, 10 seconds), and sends only its text, up to 60,000 bytes, to a separate drafting call with no tools, reserved and settled under the monthly cap like any other call. A message reads at most 2 links. The page is treated as data, never instructions: it sits between randomly named tags, the answer is only read as a catalog file, and the draft keeps at most 20 entries and drops every link and note the page gave. A draft of one place gets the member's own link, or the page's address when the link redirected within its own site. The assistant sees just how many items the draft adds and which ones the catalog has already.
- Talk to the assistant in Slack, behind the same flag (#17). With the key, the flag, and Admin's switch on, a member can message Dinnerbell directly, or mention @dinnerbell in the household channel, and Dinnerbell answers in that message's thread. A direct message thread is private to its member. A channel thread is shared, each message acts as its author, and Dinnerbell's first reply there says it sees only messages that mention it. Dinnerbell answers active members only, and ignores bots, edits, and mentions outside the household channel: nothing from anyone else is stored or sent. Replies can't mention anyone or ping the channel, and hold no links: any address in one is written so Slack doesn't link it (
hxxps[:]//example[.]com). Each member has one message answered at a time; another meanwhile gets a note that Dinnerbell is still on the last one. A direct message with a file gets "I can read only text messages." App Home shows a line saying members can message or mention Dinnerbell while the assistant answers them. Slack needs the new assistant variant of the app manifest,deploy/slack-app-manifest.assistant.yaml(deploy/slack-app-manifest.assistant.test.yamlfor a test instance); the default manifests don't change. - The assistant answers within 100 seconds, and keeps who a Slack message mentions (#17). A message that takes longer gets "I ran out of time on that one. Try asking for less at once." instead of running on after the web page stops waiting, and nothing of it is kept. In Slack, a mention of an active member reaches the assistant as that member's "Member 2", so "can <@kim> cook?" keeps its meaning, and the reply names Kim; anyone else still goes as "@Someone".
- The assistant answers questions about meal history, behind the same flag (#264). Ask "What's our most-ordered pizza place?" or "When did we last have Thai?" in any conversation, and the assistant looks it up in the meal log: each place or home meal the household ate, how often, and when last, narrowed by name, tag, kind, or dates. Each comes with its household hint, such as "Well liked", the same words every member sees on Catalog, under the same thresholds. It never says who ate, cooked, ordered, or rated, and sends nobody's own ratings or notes (ADR 0009, amended).
- The assistant shows that it's working in Slack (#265). As soon as Dinnerbell takes a message to answer, the thread shows "Dinnerbell is thinking…" with a few rotating lines. Where Slack won't show that status, Dinnerbell reacts to the member's message with ⏳ instead. Either one goes when the reply posts, and after an error or the out-of-time line. The indicator never delays or blocks the reply, and messages Dinnerbell ignores show none. The assistant manifests add the
reactions:writescope for the reaction. - The assistant drafts call actions, in any conversation, behind the same flag (#251). In a DM, on the web, or in a channel thread, a member can ask the assistant to answer in, out, or maybe; join late; vote or take a vote back; suggest a catalog item; take or give up a role; take back an offer they made; invite a guest, saved or new with the dietary needs they name, and answer for a guest they invited; or start a call, or start a called-off one again. Each change is its own draft, so "I'm in, put me down for pickup, and vote for the noodle place" gives three cards, and each Confirm runs the same service as the button on the call, as the member with a member's permissions, even for an admin. A draft says what Confirm does, such as joining late first or withdrawing role offer...
0.15.0
Security
- pydantic 2.14.2 fixes two medium-severity validation bypasses (GHSA-qpmf-fgh3-ff25 and GHSA-3r8g-cqwr-jr29). Both need a model,
TypedDict, or dataclass that allows extra fields, which Dinnerbell never uses, so neither could be reached. Routine updates come with it: pydantic-settings 2.16.2 and python-multipart 0.0.33 in the image, uv 0.13.7 for the build, and newer development tools.
Added
- Dinnerbone's Den on a call's page (#241). With fun mode on, a call's own page, the one View on web in Slack opens, now has the den at the top, beside Today, as Today has it beside the greeting. There it follows that call rather than Today's next open call: laps while it takes answers, the wheel while it's voting, eating once it's decided. Locking or marking done the call on its page celebrates as it does on Today, and its card's refresh keeps the den current. Badges still flip on Today only. With fun mode off, the page is as before.
Changed
-
A guest shows once on a call's page (#238). A guest who was in used to be listed twice: in Who's in, and again under Guests with "invited by". Now Who's in lists each guest once, marked "Guest invited by Sam", and the Guests list is gone. Everything you could do there is on the guest's row: their dietary needs, In and Out and the roles for a guest you answer for, and Take off the call. A guest who's out stays on the list as out, and one taken off the call or removed keeps their answer's row, marked "Guest". A guest with Slack who hasn't answered yet has a row marked No answer yet while answers are open, and leaves the list when answers close, as a member who never answered does. Invite a guest is where it was. The Slack call message already listed each guest once, and App Home has no roster, so they don't change.
-
Details no longer asks how many guests you're bringing (#240). On a call, guests come only from Invite a guest, which names each one and their dietary needs, so Details on the web and in Slack drops Guests and Guests' dietary needs, and keeps your eat window, a suggestion, and a note. A guest count already saved on a call keeps counting: in the head count, ranking, the decision, history, stats, and hosting badges. Offers keep their guest count, since an offer has no invitations.
-
Every "nothing" choice in a menu is in square brackets, with the same words on the web and in Slack (#239). A choice that means nothing names it, and a menu that needs a pick asks for one:
- Suggest from the catalog, and From the catalog in Add a proposal and Make an offer, now offer [Nothing from the catalog] on the web, as in Slack, instead of [Nothing] and "Something new instead". A saved guest offers [No saved guest], instead of "Someone new instead".
- Hand off coordinating on a call's page starts on [Choose someone], so you can't hand off to the first name by accident. It lists only members who can take it: once a call is decided, only those who are in, and never someone switched off. Before, it listed members a hand-off then refused. With nobody to list, the form is gone instead of showing an empty menu.
- On the web, Cuisine reads [Choose a cuisine], and Log a meal reads [Choose from the catalog]. Change the plan reads [Keep the place], [No cuisine], and [Whichever the place allows]. The catalog filters read [All kinds], [Any way], [Any meal], [Any tag], and [All], and Merge into reads [Choose a tag].
- In Slack, a menu with nothing picked shows a bracketed placeholder instead of Slack's own "Select an item": the same words as its "nothing" choice, such as [Nothing from the catalog], or [Choose someone], [Choose a way], [Choose a meal], [Choose a cuisine], [Choose from the catalog], or [Choose who ate] where it needs a pick. Who picks up in Assign roles, and a role nobody holds in Adjust, read [First who offered], which is who gets it when you leave it empty. A role in Adjust held by someone the menu can't list, such as a member made inactive, reads [Choose someone], and leaving it empty keeps them. Adjust shows [Keep the place] on its place menu, [Whichever the place allows], and [No cuisine], and Invite a guest shows [No dietary needs]. Either way in the ⋯ beside a pick is now [Either way].
The messages these menus show when you leave them empty say Choose to match: "Choose someone.", "Choose another active member.", "Choose who does it.", "Choose who coordinates.", "Choose how to get it.", and "Choose a cuisine for it". Nothing a form sends changes.
Fixed
- Dinnerbone keeps running while you scroll (#242). During a lap around the call card, scrolling paused him until it ended, and on a phone, the toolbar sliding away mid-scroll sent him back to the den to start over. Now he runs through a scroll, and when the window changes size, the phone turns, or the card grows or moves, he carries on around the card's new outline at his usual pace instead of starting over.
Upgrade notes
- Guest counts on open calls (#240): nothing in the database changes. A call open at the upgrade keeps any guest count already saved on it, and it counts until the call ends; saving Details leaves it as it is, and nobody can change it there anymore, so to bring someone else, invite them as a guest. A Details page or Slack modal opened before the upgrade still saves: its guest count and guests' dietary needs are ignored, whatever they say.
Image
ghcr.io/dsmorgan/dinnerbell:0.15.0@sha256:0ea17812b3af6a1dddbc25f21459b5725de82ecceff7ea907349c210c1d830a6
0.14.0
Security
- The base image moves to the current Python 3.12 slim digest, which has the fixed
aptfor CVE-2026-109518. Grype flagged the oldaptin 0.13.0's image at high severity. Dinnerbell never runsaptonce the image is built, so the flaw couldn't be reached in a running container, but the scan blocks CI until the image has the fix. - The image installs Debian's fixed zlib (CVE-2026-85091 and CVE-2026-76844, both high). No
python:3.12-slimdigest has it yet, so the image installszlib1g1:1.3.dfsg+really1.3.1-1+deb13u1 from Debian security until one does. Dinnerbell doesn't compress anything itself; Python and its libraries load zlib for compressed data, such as gzip.
Added
- Choose light, dark, or auto (#231, FR-64). On Preferences, and on a guest's dietary-needs page, the new Light or dark card beside Fun mode sets how your pages look: Auto, the default, matches your device as before, and Light or Dark stays that way on every device you sign in on. Your phone's address bar follows too. An admin can change a member's from Admin > Members, audited as
member.color_mode_set. The sign-in page always matches the device. - Change the place after a decision (#219). When you end up eating somewhere else, the coordinator or an admin can record it until the meal is marked done: Adjust in Slack (the coordinator), or Change the plan on the web, which is the new name for Change the time or who does what. Choose any active catalog place or type a new name, with a way the place allows. Vetoes, dietary needs, the variety window, and who offered don't block it, because it records what happened. People keep their roles if the new way still has them. The decision updates in place, each person who's in gets one message before the meal time, and after it only someone you hand off to in the same save is messaged. History, ratings, and How was it? name the new place. It's audited as
event.place_changed. Correcting the place after Mark done is a separate change (#220). - Correct the place after a meal is done (#220). When a meal was marked done before the household changed its mind, an admin can correct the place under Change the plan on the call's page: any catalog place or a new name, with a way the place allows. History, stats, ranking, and the variety window use the corrected place, and feedback on the meal moves to it. Answers that don't fit the new kind stop showing and counting until a correction brings the kind back. The meal's counts and badges follow, as when an admin corrects who did what, and it's audited as
event.place_changedwithafter_done, andevent.contributions_recountedwhen a count moved. Nobody gets a message, and the posted messages update. - Put a takeout proposal back to "either way" (#212). While voting, the coordinator or an admin can now put a proposal whose way they chose, Pickup or Delivery, back to not chosen: tap the chosen way again on the call page, or pick Either way in the ⋯ beside it on the proposals message. If someone else changed the way since your page or message showed it, Dinnerbell refuses the tap, says what the way is now, and changes nothing. The proposal keeps the way it shows, without "(chosen)", and if it wins, the decision asks the coordinator to choose, as for a proposal nobody set. The same people can do it as can choose the way. Audited as
event.way_setwithmode: null.
Changed
- The web pages have a new look: Hearth (#230). The warm clay colors are cleaned up, and every page uses the Figtree font, which Dinnerbell serves itself, so no page loads anything from another site. Every chosen control now looks the same: In, Maybe, or Out, a tag, a meal, a role you offered, and a takeout way are all filled with the accent color and its text. Vote is the exception: it stays the solid orange button until you vote, then turns into a light tint marked ✓ Voted, so it doesn't look like something left to tap. The page you're on in the menu and the tabs keeps its light tint, since it's where you are, not a choice. Preference levels keep their colors, and a chosen level now shows all four edges. Corners use one scale, and dark mode is ready to be chosen per member, not only taken from the device. Inactive members and items, and people who are out, now read in the muted text color instead of fading, so they stay readable.
- Guests no longer coordinate (#227). Only household members can. Coordinating means using Dinnerbell to steer a call, and guests have little or no access to it, so a guest with no Slack could hold coordinating with nobody able to act on it. I'll coordinate is gone from a guest's card, reminder, App Home, and call page. A guest who taps it, or Mark done, on a channel message is told why not. Hand-offs and the admin's Coordinator form list only members, and a forged request is refused. Guests can still answer In or Out, offer to cook, pick up, or order, be assigned those roles (a guest with no Slack is told through whoever invited them), and set their dietary needs. A guest can no longer close answers, move the decision time, choose the way or the roles, change the meal time, hand off, or mark a meal done, and with nobody a guest could coordinate, a tied vote no longer goes to whoever invited a guest. An admin who makes a guest a member lets them coordinate. A guest's Stats shows Quarterback only if they earned it before this. This replaces the rule from 2026-10-24.
- Vote stands out on the call page (#212). On each proposal, Vote is now the solid orange button that everyone taps; once you vote, it turns into a light tint marked ✓ Voted. Join late and vote sits in the same spot. The coordinator's and admins' controls move to a quieter row below a thin line, labeled Coordinator: Pickup and Delivery side by side, then Break the tie and Lock this, which still ask you to confirm. Their buttons are smaller, with muted text and no border until you point at or move to them, and they're still easy to tap on a phone. Shuffle proposals, above the list, has the same quiet look. A member who isn't the coordinator or an admin sees only Vote, as before.
- Lock this and Break the tie move into the ⋯ menu in Slack (#214). Everyone sees a proposal's buttons, but only the coordinator or an admin can lock it or break a tie, so Vote is now the only button beside a proposal. Lock this and Break the tie are in the ⋯ beside it, with Make it pickup, Make it delivery, and Either way. Picking either one opens a small window to confirm, because Slack allows one confirmation per menu, and anyone who can't do it is told right away. A proposal with nothing else in its ⋯ also has View on web. Buttons on messages already posted keep working until the message is next updated.
- Slack's "nothing" choices are in square brackets (#214). They read like real picks, so they're now [Nothing from the catalog], [No saved guest], and [No answer] on the rating, in the menus and in the messages that name them.
- Shorter coordination messages in Slack (#218). The direct messages about coordinating and roles now start with a bold headline, such as "You're picking up, ordering, and coordinating breakfast on Saturday, Nov 7.", with the place on its own line and short bullets for the facts and for what a coordinator can do. This covers being picked at random, being given coordinating, choosing roles, and being assigned a role. Roles read as a serial list wherever Dinnerbell lists them for you. "X assigned you this" keeps its own paragraph, above the bullets.
- The web's "nothing" choices are in square brackets too (#218). The role form and the admin Coordinator form now offer [Nobody], Suggest from the catalog offers [Nothing], and the rating in How was it? offers [No answer], matching Slack.
- Every expandable menu looks expandable (#215). On the web, the title of every menu that opens, such as Add a proposal and Admin, now has the normal text color and the
+or−marker that card headings have. Call it off stays red. - Resetting to the defaults asks first (#226). On Admin > Ranking and Admin > Badges, a reset now asks you to confirm and says what it replaces. After a reset, the page still says it happened.
Fixed
- History's meal edit no longer disagrees with correcting the place (#224). A meal from a call now has one way to change its place: Change the plan on the call's page, for admins. History's form shows the place read-only, with a link there, and refuses a changed item from a form left open, because that edit left the call, its messages, and its counts behind and deleted the meal's feedback. Meals you logged by hand and meals from offers keep their item edit. If an earlier edit left a call and its meal on different places, Change the plan now starts from the meal's place, and an admin can correct to either one, which brings them back into line. If the call's place has left the catalog, type its name with a way to correct back to it. A meal an admin deleted no longer offers the correction form.
- A History form left open can't undo someone else's change (#224). History's edit and delete forms now refuse a save when the meal's date, meal, item, or who ate changed since the page opened, and say to look again. That stops a form opened before a correction from putting the old place back and deleting the feedback that moved, and stops a second tap on Save from going through.
- Take back a choice in a Slack modal (#207). Slack can't clear a select menu once something is picked, so after picking a catalog item you couldn't write something in, and Details couldn't take back a saved catalog suggestion. From the catalog in Add a proposal and Make an offer, and **Su...
0.13.0
Added
- Away until: skip calls while you're gone (#196). Wherever a call takes answers (the call message, your Your answer card, the reminder, App Home, and the call's page), Away until… asks for the day you're back, and you're away from that call's day until then. Or set the first and last day ahead of time under Away on Preferences. Calls on those days answer you Out, marked "away until Oct 25" on the roster: the call post doesn't mention you, you get no reminder, nobody waits on you, and the call can still close early, as FR-56 says. An answer you gave already stays, and you can still tap In, or join late, on any call; that holds for that call only. Your card, Home, the call's page, and Preferences say "Away until Sun, Oct 25" with I'm back (or Clear, before it starts), which ends it and asks you again on calls still taking answers. An admin can set or clear a member's from Admin > Members > Preferences.
- Admins can see and change a member's preferences (#181). On Admin > Members, select Preferences on a member's row, or open the member and select their preferences. The page is the member's own Preferences page, with a banner that says whose it is: I can usually, reminders, dietary needs, fun mode, and every tag and item level. Each change is saved as the member's and audited with the admin as the actor and the member as the target:
member.preference_set(with the level before and after),member.settings_updated,member.needs_updated, andmember.fun_mode_set. A save of settings, dietary needs, or fun mode that changes nothing writes no audit row. The member isn't messaged, and their sign-in and sessions don't change. A member's own changes on Preferences stay unaudited, except dietary needs, which are audited asguest.needs_updated, as before. Guests have no Preferences page; an admin still changes a guest's dietary needs on their row in Guests. Preferences now says "Only you and the household's admins can see these." - Takeout gets an orderer and a pickup person (#178). A pickup meal now has two roles, Order and Pickup, and delivery keeps one, Order. By default they go to different people: the first person who offered to pick up picks it up, and the first other person with I'll order on for the call orders. Someone who usually orders but turned I'll order off isn't picked, though they would be for delivery. If nobody else has it on, the person picking up orders too, so someone who offered to pick up is still all a pickup needs. The coordinator or an admin can give one person every role. Someone who offers a pickup meal does both. The decision, App Home, role messages, and call-off messages name both roles, and Order online shows on a pickup too.
- Choose pickup or delivery during the vote (#178). While voting, the coordinator, a guest coordinator, or an admin can make a takeout proposal pickup or delivery when its place allows both: ⋯ beside it on the proposals message, or Pickup and Delivery on the call page. A proposal whose way was chosen says "(chosen)". Audited as
event.way_set. - The coordinator can move the decision time (#198). While voting, the coordinator, a guest coordinator too, can make voting close 15 or 30 minutes later, or 15 minutes earlier: Move the decision time on the call page, or in the ⋯ menu on the call message. It has the same limits as an admin's move, and the "Vote by" time updates everywhere. A time that has already passed closes voting at once, as Decide now does; a guest coordinator can't do that. An admin can use it in Slack too. Audited as
event.deadline_moved, as an admin's move is, with who moved it and as what. Neither can move a time that has already passed, before the scheduler closes it. - Reset the ranking to its defaults (#177). Admin > Ranking now has Reset to defaults below the form. Open it and select Reset ranking to put every setting on the page back to what a new household starts with: the weights, Randomness, Feedback, the number of proposals, the variety window, and the time to choose roles. Call times, skipped days, and badge counts stay as they are. A reset is audited as
household.ranking_reset. A household that upgraded to 0.11.0 has Feedback at 0 unless an admin changed it, so a reset turns ratings on. - History is more compact (#177). On a wide screen, each meal's buttons now sit in a column beside its details instead of below them. On a phone, they stay below the details but share a row where they fit, with Edit and Delete always side by side. A meal's cuisines share a line with its name, and History's buttons are now 44 pixels tall, so they're easier to tap.
- Dinnerbone's bowl and bell sit out on the floor (#177). In fun mode, the food bowl and the dinner bell over it now stand about a third of the way across the den, away from his bed of straw, instead of at the bed's edge. He still eats, nibbles, and waits at the bowl, the bell still rings over it, and he potters, and rests between laps, on the floor between the bowl and his wheel.
- Stats shows what's new, with dates (#177). On the Yours tab, Newly earned now lists the badges you earned in the last three days instead of the last two weeks. On the Household tab, Lately earned is now Newly earned, like the Yours tab, and each badge in it shows the day it was earned, in the household's time zone, beside who earned it.
Changed
- Checkboxes on Preferences are all the same size (#177). Under I can usually and Reminders, a long label no longer shrinks its checkbox, and each box lines up with the first line of its label. Fun mode is now a Show Dinnerbone's Den checkbox, like the page's other on and off settings, instead of On and Off buttons. The same checkbox fix applies wherever the app has a checkbox row, such as Schedule and the Catalog.
- Schedule sections are shorter (#177). On a screen 576 pixels wide or wider, such as a tablet or a computer, each meal's Time to answer, Time to vote, and Reminder before answers close now share one row, so a meal's section is about a quarter shorter. On a phone, they stay stacked one above the other.
- Your usual settings start your offers on (#180). Your usual offers turn on once per call, the first time you count as In, however that happens; after that the call's offers are yours. Tapping In, saving Details before you answer, claiming or being given coordinating, and joining late turn on I can cook, I can pick up, and I'll order to match Cook, Pick up, and Order on Preferences. Offering a role, or making an offer that joins the call as a pick, counts you in with only that role. Turn any offer off for that call, and it stays off: answering In again, coming back In after Out, and a refreshed card don't turn it back on. Maybe and Out turn nothing on, and an item's cook list still decides who can cook it. Preferences says so in place of "this doesn't volunteer you", and Order delivery is now Order, on Preferences and on Admin > Members.
- Today says what Start a call and Make an offer do (#177). Both stay folded, and each now has a line under its name: a call asks the household who's in and what to eat, then everyone votes on it; an offer says what you're already making or getting, so others can join. A form whose post fails opens on its error, as before. The Set up the household card at the bottom of Today is gone, because Admin and Schedule are in the menu.
- Voting picks a coordinator when nobody claimed it (#179). When answers close and the call goes on to voting with nobody coordinating, Dinnerbell picks one of the members who said In at random: never a guest, and never someone who was still a maybe. The call message and roster name them, and they get a direct message saying they were picked and what they can do: Lock this, break a tie, and shuffle the picks while voting, and once it's decided, change how you get it and who does it. They're a coordinator like any other. When the decision leaves the role unclear, they get the usual Assign roles message and the household's time to choose, 15 minutes by default and never past the meal time, before the first volunteer, if there is one, does it. They earn coordinating credit, and its badges, when the meal is done, as if they'd claimed it. They can hand it off like any coordinator, and someone can still claim it before voting starts. With no member in, nobody coordinates, as before. The pick is reproducible from the call and its run, happens once a run, and is audited as
event.coordinator_pickedand logged ascoordinator_picked. - Admins can break a tie, shuffle, and switch late joiners at any time (#179). While voting, any admin can now tap Break the tie, Shuffle proposals, or a late joiner's Taking part and Vote counts, alongside the coordinator. Before, an admin could only when nobody coordinated or a guest did. A guest coordinator still can't do these. The refusals now say "Only the coordinator or an admin can ...".
- Ordering counts on a pickup (#178). The person who orders a pickup meal now earns an Order Up count for it, apart from the pickup count. If the coordinator switches a pickup to delivery, whoever was picking up is dropped and gets no pickup count. Pickup meals done before the upgrade keep the counts they had. An admin's correction after the meal moves each role's count on its own (#162).
- The decision asks the coordinator about takeout (#178). When the winning proposal is takeout at a place that allows pickup and delivery and nobody chose its way (Dinnerbell drew it, and nobody set it during the vote), or when a role has no clear owner, the coordinator gets Assign roles...
0.12.0
Changed
- The monthly recap shows your badge art. Each member's badges in the recap now get a line naming them and a row of the same art the badge posts use, beneath it. The line names up to 10 badges, one row's worth, and counts the rest ("and 2 more badges"). A badge whose art isn't in Slack keeps its text tag, and when there's no art at all, such as when the Slack app lacks the
files:writescope, the recap is the text it was, with 6 badges a member. The recap waits for, retries, and falls back from the art the same way badge posts do. - Badges are listed rarest first. Badge posts and the recap list each member's badges by tier, highest first (Diamond, Gold, Silver, Bronze, First), then by ladder (Rare, then Occasional, then Frequent), then in the order of the badge table. Before, they followed the badge table alone, so a Diamond could be cut off ("and 6 more badges") while a First tier was named. A list cut short now leaves off the most common badges.
- Clearer failures (#153). The banner at the top of the page now says why a tap didn't save: "Not saved. Check your connection and try again." with no network, "Not saved. Something went wrong. Try again." after a server error, and "Not saved. Reload the page." when your session has expired. A request with no answer after 15 seconds gives up and says it might not have saved. Before, every failure said "Not saved. Reload the page.", and a stalled request left the button waiting with no end. A preference row that didn't save goes back to the level it last saved, and the banner stays until each card or row that failed saves, or that card refreshes.
- An error on a call card scrolls into view (#153). When a call refuses a tap, such as one that lost a race, its error at the top of the card now scrolls into view instead of staying above the screen on a tall card. With reduced motion, it jumps there without scrolling smoothly.
- A tap shows at once (#153). Buttons, preference levels, and chips now darken or lighten the moment you press them, instead of showing nothing until the save comes back, and their text keeps its contrast in both themes. A pressed chip that links shows its border. With motion allowed, a pressed control also shrinks slightly, and colors ease over about a tenth of a second, so a choice you change on a call card, such as In or I can cook, eases into place. A card's refresh that changes nothing moves nothing. With reduced motion, every change is instant.
- A slow save shows that it's working (#153). When an answer, vote, or preference takes longer than 150 milliseconds, the control you tapped dims and the pointer shows progress until it saves. A save that's faster than that shows nothing, so a quick tap doesn't flicker, and a card's refresh never dims it. Screen readers hear the card or row as busy until the new one arrives.
- A full-page form posts once (#153). Forms that load a new page, such as How was it? and Fun mode, dim their buttons while they post, and a second tap or click is ignored, so a double tap no longer posts twice. If you go back to the page, or the next page doesn't load within 10 seconds, such as when you stop it, the form works again. A form that isn't sent, because a field is missing or a catalog file is too big, isn't affected, and neither is one you send with Ctrl, Cmd, or Shift held, which can open the result in another tab or window.
- "Saved" fades on Preferences (#153). The "Saved" beside a preference you change now fades after about 2 seconds, instead of staying on every row you changed. With reduced motion, it disappears without fading. Screen readers can still read it.
Removed
- The upgrade guard for old feedback forms (#148). 0.11.0 refused a How was it? form or modal opened before the upgrade, which still asked about the food and the place, so that saving it couldn't take back your rating. Both instances now run 0.11.0, so the guard is gone. A rating is now simply required: the web form and the Slack modal always send one, because a rating, No answer at first, is always selected. A web post without one gets the Request refused page, a Slack modal without the rating closes, and one with no rating picked says "Pick a rating, or No answer." None of them saves anything.
Fixed
- The last tap is the one that sticks (#153). On a call card, tapping Maybe and then Out before the first answer came back saved Out but showed Maybe. On Preferences, tapping +1 and then +2 in the same row saved and showed +1. Now a tap on another choice replaces one still on its way, so the card or row shows and saves your last choice, and the replaced tap raises no error. A double tap on the same button sends it once: a double click on Invite no longer invites the guest twice, and +15 min no longer moves the deadline twice.
- Focus stays on what you tapped (#153). After you answer, vote, or change a preference, keyboard focus stays on that button or level instead of jumping to the top of the page, so the arrow keys keep moving through a preference's levels.
- Open calls keep refreshing (#153). With three or more open calls on Today, the middle cards' refreshes were dropped, and a refresh that answered after a tap could undo what the tap showed. Now each card refreshes on its own, a tap replaces a refresh in flight, and a refresh never starts while a tap is saving. A card skips its refresh only while you type in one of its fields or have one of its forms open, not just because a button in it has focus, and a refresh no longer dims the card's buttons.
- Notices on History and the Catalog show in what you land on (#153). After you save feedback, log a meal, or edit one, History scrolls to that meal, and after you add or edit a catalog item, the Catalog scrolls to it. Their notices, such as "Thanks for the feedback!" and "Changes saved.", were off screen at the top of the page. A notice now shows inside the meal or item, and the entry is highlighted for a moment and then fades. With reduced motion, the highlight stays and nothing moves. "Meal deleted." has no meal to land on, so it stays at the top, as does a notice whose meal or item isn't on the page, such as an item you deactivated. Any page that scrolls to something, such as History, the Catalog, or a row on Preferences, no longer hides it under the sticky top bar, or under the test instance's banner.
- Badge icons no longer drop to text when one new badge's art fails to upload. When a post needed art for a new badge tier and the upload failed or took longer than 3 seconds, every badge after it, in alphabetical order by badge, showed as text, even if its art was already in Slack. Art uploaded earlier in the same post was dropped too. Now only the badge whose upload failed shows as text. This affects badge posts, the recap, and App Home.
- Forgotten badge art uploads again in the background. When Slack refuses badge art and Dinnerbell forgets the files,
dinnerbell servestarts uploading the missing tiers again in the background, as it does after startup, so the next post doesn't wait for them. - A History or Catalog page that isn't a number shows the first page. An address such as
/history?page=abcor/catalog?q=thai&page=2.5showed Request refused. It now shows the first page, and the Catalog keeps your search. A page number past either end still shows the nearest page. - A correction after the meal moves the count and the badges (#162). When an admin corrects who cooked, picked up, or ordered after a meal is done, the meal's count for that role now moves to the person who has it. They earn any badge the count reaches, announced like any other and celebrated by the den. The person who lost the role loses each badge tier their counts no longer reach on the current counts, even a tier first earned at a lower count before an admin raised it. A pending one is never announced or celebrated. One already announced leaves Stats, App Home, the household's newest badges, and future recaps; a post already sent or queued in Slack stays. Correcting it back restores both. Each correction that moves a count is audited as
event.contributions_recounted, with the badges taken back and awarded. Before, a correction after done changed the record but not the counts. The fix isn't retroactive: a call corrected before this release keeps its old counts. To bring one up to date, correct its role again, for example set it to nobody and then back to whoever did it.
Upgrade notes
- Badges: revision
0024_badge_award_autoincrementrebuilds the badge award table on the first start, keeping every award, so the ID of a badge taken back is never given to another. It also starts new IDs above every member's den marker (fun_seen_award), so no new badge goes uncelebrated. To go back to 0.11.0, restore the backup you took before the upgrade.
Image
ghcr.io/dsmorgan/dinnerbell:0.12.0@sha256:cf41228bbfae27c3d1edc267596c4f8eeaa09ec4e2a3e98d7f03d9cceb48bcc5
Dinnerbell 0.11.0
Added
-
Ratings move your own score (#18, FR-55, ADR 0008). When you rate a meal, your score for that place or recipe moves toward your rating, from −2 for Hated it to +2 for Loved it: halfway, or three-quarters of the way for Hated it and Didn't like it. The change halves every 3 months, counts only on calls you eat at, and never vetoes anything. Logged meals count. Setting a score on Preferences, even back to 0, replaces your earlier ratings of it. Preferences shows you, and only you, what your ratings make your score, such as "From your ratings: about +1".
-
A hint for each place, from the whole household. Once two people have rated a place, everyone sees Well liked, Mixed reviews, or Not well liked, without names, and recent ratings count more. The most important problem checked in the last 3 months adds to it, as in "Mixed reviews · recently late", or shows alone, as in "Recently cold". The hint is the first reason on a drawn pick, on the web and in Slack, and shows on the catalog. Words written for Other are never shown.
-
Feedback on the Ranking tab of Members: how far each rating pulls a person's score, 0 (off), 1, or 2. A new household starts at 2. Hints show at every setting.
-
Adjust the plan in Slack (#149). Once a call is decided, the coordinator taps Adjust on the decision message, their App Home card, or the message saying a guest with a role left, and one modal changes the meal time, who cooks, picks up, or orders (someone who's in), and who coordinates. It saves only what they changed from what the modal showed, so a change made elsewhere meanwhile, such as with Assign roles, is never written back, and hands off last. A refusal, such as a meal time before the decision, shows next to its field without saving anything; if a later part is refused after an earlier one saved, the reply says which. Everyone sees Adjust on the decision message; anyone but the coordinator who taps it is told why not, an admin included. Someone the coordinator assigned is told they can ask the coordinator to pick someone else with Adjust.
-
Adjust switches how you get it (#154). When the decided place allows more than one way, the coordinator's Adjust modal has How (cook, pickup, or delivery), and its Who does it field assigns that person the chosen way, as Assign roles does: switching pickup to delivery with Alex selected makes Alex the one who orders, and they're told. Someone who can't do it that way, such as someone off a home meal's cook list, is refused next to the field. On the web, the coordinator's Assign roles form already switches the way at any time until the meal is done.
-
Coordinating, a page for the household: what a coordinator is, how you become one, what you can do while answering, voting, and after the decision, in Slack and on the web, what an admin can do beyond that, and what happens when nobody coordinates or someone drops out. The README links it, with the other household guides.
-
Stuck calls show on
/healthzand Admin (#142). A call whose next scheduler step has been due for more than an hour, because the step keeps failing, is stuck./healthzreports how many asstuck_callsand sets"status": "degraded"with HTTP 200, so the container health check doesn't restart Dinnerbell, which can't fix the step. The scheduler checks once per tick, so/healthzruns no extra queries. A banner on every Admin tab lists each stuck call with its meal, day, state, and how long it has been stuck, and links to the call, where you call it off (or re-run it, for a voting or decided call). A call that can't be checked counts as stuck, for an unknown time. A step that fell due while Dinnerbell was down counts from the start, so a call that catches up after a restart isn't stuck. -
Optional: start at boot on podman (#135). Rootless podman has no daemon, so after a reboot Dinnerbell stayed down until someone ran
podman-compose up -d.deploy/dinnerbell.serviceanddeploy/dinnerbell-test.serviceare systemd user units that runpodman-compose up -danddeploy/dinnerbell-test up -dat boot and stop them at shutdown. They're in the install bundle, and "Start at boot" in docs/setup.md installs them. Rootful Docker needs neither: its daemon restarts the container. At shutdown they runstop, so the containers and their logs survive a reboot, and whenupexits with an error, they try again 30 seconds later, a few times. On systemd older than 244, such as RHEL 8, addRestart=noin a drop-in. CI checks both units withsystemd-analyze verify.dinnerbell initmentions them in one optional line at the end. -
History and the Catalog come in pages (#153). History shows 20 meals a page, still grouped by week, and the Catalog 20 matches a page, with Newer and Older (or Previous and Next) around "Page 2 of 5". The Catalog's page links keep your search and filters, so a page's address is a bookmark. A page past either end shows the nearest page. Logging, editing, or deleting a meal, giving feedback on it, and adding or editing a catalog item return to the page that lists it.
-
Stats has two tabs (#153), like Admin's: Yours, with your badges and counts, and Household, at
/stats/household, with the household's totals and newest badges. Badge posts and the monthly recap in Slack link Household; App Home's Stats link stays on Yours. Guests see only their own badges, as before, and a guest who opens Household lands on them. -
Documentation only: "Switch between a clone and the bundle" in docs/setup.md moves an install from a git clone to the release bundle, or back, keeping both instances' data volumes,
.env,.env.test,secrets/,secrets-test/, andcompose.override.yaml. It replaces 0.10.0's upgrade note, which said to copysecrets/: your account can't read the secret files, so they have to be moved. -
Fun mode: Dinnerbone's Den (#153, FR-62). Dinnerbone, the hamster in the logo, now lives in a den beside your greeting on Today: a bed of straw with his bowl and the dinner bell, and his wheel. He follows the next open call. While answers are open, he runs laps around the call's card; while it's voting, he runs in his wheel; once it's decided, he eats at his bowl; once it's done, he sleeps in the straw. He walks between them as the call changes, without a reload. With no call, he follows the clock: a nibble at breakfast, pottering about at lunch, a doze in the afternoon, waiting at his bowl at dinner, and asleep late at night, unless a call keeps him up. The den's light follows the household's time of day, and the season's weather falls in the den and down the page's edges, with snow, leaves, or a puddle that grow as the season goes on; he shakes the snow off his wheel before it turns. Tap him and he hops and a heart pops. Celebrations: tap Lock this on Today and the bell rings and he sprints to his bowl ("Pad thai it is!"); tap Mark done and he pats his belly and waddles to bed; earn a badge and he backflips the next time you open Today, once. Everyone else gets a quiet caption, with no animation, and so does everyone when a call is decided by the vote or in Slack. With reduced motion, he holds still and celebrations are a caption. It never makes a sound. A long name shrinks the greeting to fit beside him, then wraps. It's on by default: members turn it off with Fun mode on Preferences, and guests on their dietary-needs page, and only you change yours. With it off, pages load none of it and are exactly as before.
Changed
- Layout fixes, mostly for phones (#153). Card titles on Schedule (Dinner, Lunch, Breakfast) and on Admin's Ranking and Badges tabs sit inside their cards instead of on the border, and those cards have room between fields. The navigation's links take two even rows on a phone instead of a ragged second row. Taps are easier: the logo, every + heading that opens a section, the tabs, the tag names on Tags, a call's title, and the catalog's meal and tag chips are at least 44 pixels tall to tap. On History, How was it? no longer touches the line above it.
- Whoever coordinates is in (#154). Tapping I'll coordinate changes your answer to In if you said Out or Maybe or hadn't answered, and so does being handed coordinating or assigned it by an admin. During the vote, you join late, as I'm in (late) does, but your vote counts, as a coordinator's always did; a late joiner who takes it on gets a counting vote too. A guest who coordinates is in but never late, so their dietary needs keep filtering the proposals. Someone a hand-off or an admin put in this way gets a direct message saying so. Saying Out ends your coordinating, as does being switched off as a late joiner, still being a maybe when answers close, or being deactivated by an admin: nobody coordinates, the call's messages say so, and anyone can tap I'll coordinate. Once a call is decided, only someone who's in can be handed coordinating or assigned it. A late joiner the coordinator switched off can't claim it, be handed it, or be assigned it. Each release is audited as
event.coordinator_released. The Home reply says "You're in, and coordinating dinner." - Someone assigned after a hand-off is told whom to ask (#154). When one Adjust both assigns a role and hands off coordinating, the assignee's message says to tell the coordinator, who can pick someone else with Adjust, instead of the one who just handed off.
- Whoever loses a role is told (#154). When the coordinator or an admin gives your cooking, pickup, or ordering to someone else before the meal time, you get "Sam changed the plan for dinner on Thursday, Oct 22: you're no longer picking up." From the meal time on, a change corrects the record o...
0.10.0
Added
- Install without cloning (#33). Each release attaches
dinnerbell-X.Y.Z.tar.gzand its SHA-256:compose.yamlpinned to the release,compose.secrets.yaml,.env.example, both Slack manifests,deploy/dinnerbell-testwith its compose files, andINSTALL.md. CI builds it from the tag and attests it, sogh attestation verifycovers it like the image. docs/install.md installs from it in eight steps. dinnerbell initwrites a new env file. It asks for the hostname, admin email, time zone, household name, and the Slack app's values, with a hint for each; generatesDINNERBELL_SECRET_KEY; and checks the result asdinnerbell config checkdoes. Secrets are read without echo and never printed. It writes to--output FILEwith mode 600, or to standard output when that isn't a terminal.init --testwrites a test instance's file and refuses production's secrets, client ID, and hostname from.env.
Changed
- Documentation only: step 9 of the setup guide again explains that
DINNERBELL_BASE_URLmust match the public URL, whatDINNERBELL_ADMIN_EMAILdoes, thatDINNERBELL_HOUSEHOLD_NAMEandDINNERBELL_TIMEZONEapply on first start only, and which secret keys Dinnerbell refuses. 0.9.1's rewrite had dropped these notes. - Badges climb three ladders (#130). Frequent (1, 10, 50, 100, 200) keeps the meal badges; Occasional (1, 5, 20, 50, 100) is for Bright Idea and Good Host; Rare (1, 3, 10, 25, 50) is for On a Roll, Scout, and Explorer, so every Diamond is within reach. Stats and App Home show each badge's next step on its own ladder.
- On a Roll has a grace week. A run survives one missed week, which doesn't count toward it; two missed weeks in a row still end it.
- Admin > Badges edits the three ladders, five counts each, validated as before, with Reset to defaults. Each save and reset is audited. The
badge_thresholdssetting holds one list per ladder; a single list from an earlier version is read as the Frequent ladder. - Tiers that the new ladders or the grace week put in reach are awarded quietly, as when an admin lowers a threshold, so the channel gets no burst of posts.
- Documentation only: the README opens with what Dinnerbell needs (a container host, a Slack workspace, and an HTTPS hostname), a diagram of how the pieces connect, and how a dinner works in five steps (#34).
Upgrade notes
- Badges: on the first start, members may receive badge tiers quietly: the new ladders and On a Roll's grace week put them in reach. Nothing is posted to Slack for them, and no earned tier is removed. A custom ladder you saved earlier becomes the Frequent ladder. No database revision ships for this.
- Install bundle: optional. An install from a git clone keeps working, and upgrades the same way. To move to the bundle, see docs/install.md; keep the directory name
dinnerbellso compose finds the same data volume, and copy.env(and.env.test,secrets/,secrets-test/if you use them) into it.
Image
ghcr.io/dsmorgan/dinnerbell:0.10.0@sha256:977e7807f9cd7bb79ed966522dafbd6402c866831f2e65aab290467369fe6e80
Install bundle
dinnerbell-0.10.0.tar.gz and its .sha256 are attached and attested. See docs/install.md.
Dinnerbell 0.9.1
Fixed
- An upgrade to 0.9.0 with the secrets still in
.envdidn't start. 0.9.0'scompose.yamlmounted four secret files unconditionally, so podman-compose stopped withstatfs .../secrets/DINNERBELL_SECRET_KEY: no such file or directorywhen they didn't exist. Secret files are now optional.compose.yamlreads the secrets from.envagain, as in 0.8.0, and keeps 0.9.0's resource limits, log rotation, and other settings. The newcompose.secrets.yamlmounts the files when you add it:podman-compose -f compose.yaml -f compose.secrets.yaml up -d.deploy/dinnerbell-testadds it, pointed atsecrets-test/(by the newdeploy/compose.test-secrets.yaml), when any of the four files is there, and then requires all four; otherwise test reads its secrets from.env.test. Its shared-secret check compares production and test however each holds them. A secret in an env file stays supported: Dinnerbell logs a warning for each one at start, and the warning no longer says a later release ignores it..env.exampleand.env.test.examplelist the four secrets again, and "Keep secrets in files" in docs/setup.md is now an optional section. The placeholder-key check from 0.9.0 is unchanged.
Changed
- Documentation only: the setup guide no longer has a "Set the trusted proxy" step, its
.envtemplate line, or the "Rate limiting blocks everyone at once" troubleshooting row.DINNERBELL_TRUSTED_PROXIESstays an optional setting, described in the configuration reference and.env.example: set one proxy address, never a range, and never an address that other clients share, such as a container gateway. Behavior and defaults are unchanged.
Added
.github/CODEOWNERSassigns the owner to CI, the Containerfile, dependency locks,compose.yaml,compose.secrets.yaml,deploy/, andscripts/.
Upgrade notes
- Back up first. No database revision ships in this release. The database stays at the revision 0.8.0 left it, so rolling back is a restore of that backup and the 0.8.0 image (or the 0.9.0 image, with secret files).
- Secrets in
.env: no action needed. Check outv0.9.1, pull, and recreate the service as usual (podman-compose pull && podman-compose down && podman-compose up -d). Dinnerbell starts and logs one warning per secret in.env. To clear the warnings, follow "Keep secrets in files" in docs/setup.md; it's optional. - Already created the secret files and removed the four lines from
.env? Add the override to everyup:podman-compose -f compose.yaml -f compose.secrets.yaml up -d(Docker:docker compose -f compose.yaml -f compose.secrets.yaml up -d). Or put the four lines back in.envand runupas usual. Without either, Dinnerbell stops at start withDINNERBELL_SECRET_KEY is required but not set. - Test instance: nothing to do.
deploy/dinnerbell-testusessecrets-test/when it holds the files, and.env.testotherwise. Ifsecrets-test/holds some of the four files but not all, it refuses to start and names the missing one. - Upgrading from 0.8.0 or earlier: also read the 0.9.0 upgrade notes below, but skip its hard stop: you no longer need secret files before
up.
Image
ghcr.io/dsmorgan/dinnerbell:0.9.1
Digest: sha256:863638f71ee31dd607aea03e4c27f0a7e170bda8eb350e891f2d03d943a31913
Verify:
gh attestation verify oci://ghcr.io/dsmorgan/dinnerbell:0.9.1 --repo dsmorgan/dinnerbell --signer-workflow dsmorgan/dinnerbell/.github/workflows/ci.yml --source-ref refs/tags/v0.9.1