Skip to content

chore(deps): update askama_axum requirement from 0.4 to 0.5#6

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/askama_axum-0.5
Open

chore(deps): update askama_axum requirement from 0.4 to 0.5#6
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/askama_axum-0.5

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot Bot commented on behalf of github May 25, 2026

Updates the requirements on askama_axum to permit the latest version.

Commits
  • 08bf32b Bump version number to 0.5.0
  • 54f0549 Rename and document top-level Generator::build() method
  • 36b0691 Reorder methods in Generator to aid readability
  • 34fcbf0 Update documentation around extensions and escape modes
  • 7247a25 Rewrite escapable() to prevent duplication
  • 7c29bf7 Extend escaping according to OWASP recommendations
  • df2637c Return MarkupDisplay from json filter
  • e559ed4 Move JSON test into filters test module
  • 07e9b30 Move escaping tests into a separate module
  • 92d93e0 Add test case for inferred escape mode
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels May 25, 2026
Updates the requirements on [askama_axum](https://github.com/rinja-rs/rinja) to permit the latest version.
- [Release notes](https://github.com/rinja-rs/rinja/releases)
- [Commits](askama-rs/askama@0.4.0...0.5.0)

---
updated-dependencies:
- dependency-name: askama_axum
  dependency-version: 0.5.0+deprecated
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title build(deps): update askama_axum requirement from 0.4 to 0.5 chore(deps): update askama_axum requirement from 0.4 to 0.5 May 29, 2026
@dependabot dependabot Bot force-pushed the dependabot/cargo/askama_axum-0.5 branch from b1d6a36 to 5974086 Compare May 29, 2026 13:26
podheitor pushed a commit that referenced this pull request May 31, 2026
Recurring meetings stored only an `is_recurring` bool that was never expanded
into instances. Add an RFC 5545 `rrule` column (migration + down) and wire it
end to end through the shared expresso-rrule engine:

- domain: `Meeting.rrule`/`NewMeeting.rrule`, all SQL column lists updated,
  `update` gains a tri-state rrule param, and `Meeting::expand_instances(from,to)`
  projects a recurring meeting's scheduled_for/ends_at into concrete occurrences
  (falls back to a single clamped instance when not recurring / no rule).
- api: create + patch accept and validate `rrule` (rejected if unparseable);
  new `GET /api/v1/meetings/:id/instances?from=&to=` returns the expansion,
  participant-gated.

Closes roadmap #6. 151 meet tests pass (incl. 7 new).
podheitor pushed a commit that referenced this pull request May 31, 2026
… — sprint #6

Builds on sprint #5 (CUTYPE parsing) to complete roadmap #10's larger half: a
room/equipment registry and conflict detection.

- migrations calendar_resources (registry: email/name/kind/capacity, UNIQUE per
  tenant) + calendar_event_resources (per-event booking index), both +down.
- EventRepo now also syncs booked resources: sync_resources extracts the event's
  CUTYPE=ROOM/RESOURCE attendee emails (lowercased, deduped) and re-indexes them
  delete-then-insert in-tx on create/update/replace_by_uid, alongside attachments.
- domain/resource.rs: ResourceRepo (create/list/get/delete) + conflicts() — a
  self-join on calendar_event_resources sharing a resource_email whose events
  overlap in time (stored dtstart/dtend, no RRULE expansion, matching the
  existing events-conflicts endpoint).
- api/resources.rs: GET/POST /api/v1/resources, GET/DELETE /:id, and
  GET /:id/conflicts?from=&to= (404 if the resource isn't registered).
- error: new ResourceNotFound(Uuid) → 404.

Closes roadmap #10. 567 calendar lib tests pass (incl. 8 new resource/booking
tests).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants