2024-12-18 Meeting notes

@Adam Stankiewicz

[question] Did we want to have an auto-sync workflow release-22.x → release-23.x?

For example, https://github.com/openedx/paragon/pull/3125 merged into release-22.x but is not carried over to release-23.x or next.

https://github.com/openedx/paragon/pull/3370

@Brian Smith : I’m hesitant to auto-sync to a release branch. Auto-sync to next isn’t an issue because we have time to test/verify before shipping a new version, but having the latest 23 release break because of a bad auto-sync is something I’d like to avoid.

@Adam Stankiewicz : Totally reasonable. Is the intent then that we’ll manually want to bring new commits (e.g., the one from PR linked above) that are relevant from release-22.x → release-23.x?

@Brian Smith : We could even set up an auto-sync workflow but have it not auto-merge, I just want to make sure we have a chance to do some light testing of the changes before making new releases

@Adam Stankiewicz

@Adam Stankiewicz

Updating “Usage Insights” GitHub Action workflows for new release branches:

https://github.com/openedx/paragon/pull/3372

Relates to https://github.com/openedx/paragon/issues/3364

@Adam Stankiewicz

[inform] Fixes a minor grammar issue in the custom file header output in CSS files by style-dictionary.

(To merge into release-23.x)

https://github.com/openedx/paragon/pull/3371

@Brian Smith

From https://github.com/openedx/paragon/pull/3367

This PR necessarily bumps the version of sass used via transitive dependencies. Will this version bump cause issues for Paragon consumers (if we change the sass code to the new version)?

@Brian Smith

I made a few issues (most feel like post-23-release cleanup), looking through those could be nice https://github.com/openedx/paragon/issues