Skip to content

revel-backend

v1.72.0 Feature

This release adds 2 notable features for engineering teams evaluating rollout.

Published 10d Productivity & Wikis
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Affected surfaces

auth

Summary

AI summary

Organizers can opt‑in to accept short notes with RSVPs via accept_rsvp_notes.

Changes in this release

Feature Medium

Adds optional attendee note on RSVPs (opt‑in per event)

Adds optional attendee note on RSVPs (opt‑in per event)

Source: llm_adapter@2026-07-16

Confidence: low

Feature Low

Allows organizers to opt‑in per event for accepting RSVP notes (≤500 chars)

Allows organizers to opt‑in per event for accepting RSVP notes (≤500 chars)

Source: granite4.1:30b@2026-07-16-audit

Confidence: low

Bugfix Medium

Fixes CI to authenticate GHCR publish using GITHUB_TOKEN instead of a PAT

Fixes CI to authenticate GHCR publish using GITHUB_TOKEN instead of a PAT

Source: llm_adapter@2026-07-16

Confidence: high

Full changelog

Added

  • RSVP Notes: organizers can opt in per event (accept_rsvp_notes, off by default) to accepting a short plain-text note (≤500 chars) with RSVPs — e.g. dietary info or "arriving late"
    • POST /events/{id}/rsvp/{answer} accepts an optional {note} body; each submission overrides the stored note (omitted/empty clears it), and the note is returned in the RSVP response, GET /my-status, and the user's RSVP list
    • Guest RSVPs carry the note through the confirmation email; if the organizer disables notes before the guest confirms, the note is dropped without failing the confirmation
    • Staff RSVP_CONFIRMATION/RSVP_UPDATED notifications include the note, and note-only changes now trigger RSVP_UPDATED (previously only status changes did)
    • Event-admin RSVP create/update accept note regardless of the flag, for offline/phone RSVPs
    • accept_rsvp_notes propagates from a series template to future unmodified occurrences

What's Changed

  • fix(ci): authenticate GHCR publish with GITHUB_TOKEN instead of a PAT by @biagiodistefano in https://github.com/letsrevel/revel-backend/pull/709
  • feat(events): optional attendee note on RSVPs (opt-in per event) by @biagiodistefano in https://github.com/letsrevel/revel-backend/pull/711
  • chore(release): v1.72.0 by @biagiodistefano in https://github.com/letsrevel/revel-backend/pull/713

Full Changelog: https://github.com/letsrevel/revel-backend/compare/v1.71.2...v1.72.0

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track revel-backend

Get notified when new releases ship.

Sign up free

About revel-backend

The Django backend of the Revel event platform project

All releases →

Related context

Related tools

Earlier breaking changes

  • v1.72.1 Makes payment base fields (`amount`, `currency`, `platform_fee`) read-only
  • v1.72.1 Restricts organization ownership transfer to superusers only
  • v1.71.0 Checkout flow now uses a two-step reserve then session creation process.
  • v1.68.0 check-in endpoint path renamed to use ticket code (UUID or series:<uuid>) instead of ticket ID.

Beta — feedback welcome: [email protected]