mitodl / mitodl/ol-analytics-api

Release ol-analytics-api 2026.9.17.1

Open
#65 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

release
Dominant language
Python
Stars
0
Forks
0
Avg merge
5d 12h
Merged PRs (30d)
18

Description

Release 2026.9.17.1

Tobias Macey
  • docs: B2B learner records spec and provider-access decision (#55) by tmacey@mit.edu
  • feat(b2b_learner_records): add the learner-records tenant (#56) by tmacey@mit.edu
  • fix(sentry): cap request bodies at 1KB and scrub Postgres DETAIL rows (#54) by tmacey@mit.edu
  • chore(deps): update Python lockfile to latest patch/minor versions (#61) by tmacey@mit.edu
  • Add self-documenting descriptions to analytics response fields (#57) by tmacey@mit.edu
renovate[bot]
  • chore(deps): update python docker tag to v3.14 (#48) by 29139614+renovate[bot]@users.noreply.github.com
  • chore(deps): update astral-sh/setup-uv action to v10 (#50) by 29139614+renovate[bot]@users.noreply.github.com
  • chore(deps): update actions/checkout action to v7 (#49) by 29139614+renovate[bot]@users.noreply.github.com
  • chore(deps): update zizmorcore/zizmor-action action to v0.6.3 (#47) by 29139614+renovate[bot]@users.noreply.github.com
  • chore(deps): pin dependencies (#46) by 29139614+renovate[bot]@users.noreply.github.com
  • chore(deps): lock file maintenance (#51) by 29139614+renovate[bot]@users.noreply.github.com

This release was automatically generated by the Concourse release pipeline.
Closing this issue will trigger the production deployment.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

This is an automatically generated release checklist, and it names no source file or test to change. Read the listed issues and the Concourse release pipeline, then verify that the checklist is complete before taking the deployment-triggering action of closing the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
10/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.