Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(opa): Update container images to 1.0.1 ahead of Stackable Release 25.3.0 #998

Closed
15 of 19 tasks
Tracked by #964
sbernauer opened this issue Feb 10, 2025 · 2 comments
Closed
15 of 19 tasks
Tracked by #964
Assignees
Labels
release/25.3.0 release-note/action-required Denotes a PR that introduces potentially breaking changes that require user action.

Comments

@sbernauer
Copy link
Member

sbernauer commented Feb 10, 2025

Part of #964.

However, this is the single patch level update we have this release, so there is no dedicated tracking issue.

  • Add: 1.0.1
  • Remove: 1.0.0

Tip

Please add the scheduled-for/20XX-XX label, and add to the Stackable Engineering project.

Update tasks

Preview Give feedback

Related Pull Requests

Preview Give feedback
  1. 0 of 15
    razvan
  2. razvan
  3. 0 of 15
    razvan
  4. 0 of 15
    razvan
  5. 0 of 15
    razvan
  6. 0 of 15
    razvan
  7. 0 of 15
    razvan

Tip

Delete any items that do not apply so that all applicable items can be checked.
For example, if you add release notes to the documentation repository, you do not need the latter two criteria.

This list should be completed by the assignee(s), once respective PRs have been merged. Once all items have been checked, the issue can be moved into Development: Done.

Acceptance

Preview Give feedback
Testing instructions
# See the latest version at https://pypi.org/project/image-tools-stackabletech/
pip install image-tools-stackabletech==0.0.13

bake --product opa=x.y.z # where x.y.z is the new version added in this PR

kind load docker-image oci.stackable.tech/sdp/opa:x.y.z-stackable0.0.0-dev

# Change directory into the opa-operator repository and update the
# product version in tests/test-definition.yaml
./scripts/run-tests --test-suite smoke-latest # or similar

Please consider updating this template if these instructions are wrong, or
could be made clearer.

@sbernauer sbernauer moved this to Ready for Development in Stackable Engineering Feb 10, 2025
@sbernauer sbernauer self-assigned this Feb 10, 2025
@sbernauer sbernauer moved this from Ready for Development to Development: In Progress in Stackable Engineering Feb 10, 2025
@sbernauer sbernauer assigned razvan and unassigned sbernauer Feb 17, 2025
@razvan razvan moved this from Development: In Progress to Development: Waiting for Review in Stackable Engineering Feb 17, 2025
@razvan razvan moved this from Development: Waiting for Review to Development: Done in Stackable Engineering Feb 17, 2025
@sbernauer
Copy link
Member Author

Thanks @razvan!

@NickLarsenNZ
Copy link
Member

Moved from #969 (comment).


Release Notes snipped:

Changes to Rego-Rules:

  1. BREAKINGUsing if for all rule definitions and contains for multi-value rules is now mandatory, not just when using the rego.v1 import.
  2. Other new keywords (every, in) are available without any imports.
  3. Previously requirements that were only run in "strict mode" (like opa check --strict) are now the default. Duplicate imports and imports which shadow each other are no longer allowed.

@NickLarsenNZ NickLarsenNZ added the release-note/action-required Denotes a PR that introduces potentially breaking changes that require user action. label Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release/25.3.0 release-note/action-required Denotes a PR that introduces potentially breaking changes that require user action.
Projects
Status: Development: Done
Development

No branches or pull requests

3 participants