joeyr
released this
2026-10-07 19:16:25 -05:00
| 12 commits to main since this release
Fixed
list_announcements returned only the last fourteen days, and said nothing about
it. It called /api/v1/announcements with no start_date, and Canvas documents an
omitted one as fourteen days ago. So "recent" in the description was not a choice; it
was a fortnight nobody had picked, and a course whose last announcement was three
weeks old answered exactly like a course with none. Found while filing a term's
announcements into notes, when everything from its first five weeks was out of reach.- Both ends of the window now go on every request. Canvas also documents an omitted
end_date as twenty-eight days after the start, so sending a start alone would have
moved the window rather than opened it. The default start is a floor before Canvas
existed (ANNOUNCEMENTS_FLOOR) and the end is a day past now, so the default read is
every announcement in the active courses.
Added
since on list_announcements, an ISO date or datetime, for "anything new this
week" without the whole term. A bare date, or a time with no offset, is read in the
tenant's timezone, because in UTC "since the first" starts the evening before. A value
that does not parse is refused before any request, naming the argument, rather than
reaching Canvas as a 400 that names nothing.- Announcements come back newest first, sorted here rather than trusted from the
endpoint, whose order nothing has measured.
- An empty answer says which kind it is, by the rule
get_submission_feedback set
in 0.55.0: a since read that finds nothing says it was bounded and says nothing about
earlier weeks; only an unbounded read may say the courses have no announcements.
Changed
- The tool description no longer says "recent" and states that the default is the whole
term. Reconnect the Canvas connector after deploying, or Claude keeps the old one.
Downloads