Skip to content

perf: teak release support#129

Merged
luisfelipec95 merged 11 commits into
masterfrom
lfc/teak-support
Jun 19, 2025
Merged

perf: teak release support#129
luisfelipec95 merged 11 commits into
masterfrom
lfc/teak-support

Conversation

@luisfelipec95

Copy link
Copy Markdown
Contributor

Description

This PR aims to support the new Teak release

Testing instructions

1, Create a Teak environment using Tutor.
2. Install eox-tagging using this branch you can follow the official tutor documentation.
3. Follow the test cases file.

@luisfelipec95 luisfelipec95 requested a review from a team as a code owner June 9, 2025 23:28
@luisfelipec95 luisfelipec95 changed the title Lfc/teak support perf: teak release support Jun 9, 2025

@magajh magajh left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@luisfelipec95 Please check if any of the comments I left in eduNEXT/eox-core#319 apply to this PR as well.

Also, could you please let us know if the test cases have been fully tested and we have made sure everything is working fine?

@magajh magajh left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@luisfelipec95 have we checked that the workflows are up to date with the latest dependencies?

Comment thread requirements/base.in Outdated
@luisfelipec95

Copy link
Copy Markdown
Contributor Author

The dependencies are up to date and the test cases were run in the remote environment.

@magajh

magajh commented Jun 19, 2025

Copy link
Copy Markdown
Contributor

@luisfelipec95 why are the integration tests failing? can we please fix this before merging this PR?

@luisfelipec95

Copy link
Copy Markdown
Contributor Author

Regarding the workflow error:

Currently, eox-tagging uses edx-opaque-keys[django]==2.13.0, which I believe is causing the error. If I update it to version 3.0.0, it creates an incompatibility with eox-core.

With the teak release of eox-core, the update to edx-opaque-keys[django]==3.0.0 is also being made. Therefore, once the new release of eox-core is available, I can specify that new version in eox-tagging and update opaque-keys to ==3.0.0.

@magajh

magajh commented Jun 19, 2025

Copy link
Copy Markdown
Contributor

Regarding the workflow error:

Currently, eox-tagging uses edx-opaque-keys[django]==2.13.0, which I believe is causing the error. If I update it to version 3.0.0, it creates an incompatibility with eox-core.

With the teak release of eox-core, the update to edx-opaque-keys[django]==3.0.0 is also being made. Therefore, once the new release of eox-core is available, I can specify that new version in eox-tagging and update opaque-keys to ==3.0.0.

@luisfelipec95 great. Let's do the eox-core release first then, and after the dependency is updated here and the tests are passing, I'll approve this PR so we can merge it.

@magajh magajh self-requested a review June 19, 2025 23:17
@luisfelipec95 luisfelipec95 merged commit e199c7e into master Jun 19, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants