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

Bump version to 0.7.0 #80

Merged
merged 1 commit into from
May 7, 2024
Merged

Conversation

dosas
Copy link
Contributor

@dosas dosas commented Apr 25, 2024

It would be nice to have a new release

should be merged after #81

@dosas
Copy link
Contributor Author

dosas commented May 6, 2024

@ezr-ondrej Are you fine with a new release?

Copy link
Member

@ezr-ondrej ezr-ondrej left a comment

Choose a reason for hiding this comment

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

I'm but we will also should also plan to do releasing and packaging for it.
I'm happy to tag the new version, but I don't think I should (just because I'm not very active and I might not be around to fix it if it breaks ;) )
@evgeni would you do it?

@dosas
Copy link
Contributor Author

dosas commented May 6, 2024

I'm but we will also should also plan to do releasing and packaging for it. I'm happy to tag the new version, but I don't think I should (just because I'm not very active and I might not be around to fix it if it breaks ;) ) @evgeni would you do it?

Makes sense

AFAIK:

  • Releasing is now (due to the release workflow) just pushing/creating a tag.
  • The new gem versions are automatically picked up by foreman-packaging

@evgeni
Copy link
Member

evgeni commented May 6, 2024

Correct, release is just a tag now, and packaging is automatically updated once a week, so no "manual" work is needed.

What I do not know is how quickly we'd see problem reports (if any, e.g. the Foreman nightly pipelines don't test LDAP), but I guess that shouldn't block us from releasing.

@ezr-ondrej
Copy link
Member

Lets push some buttons, then :)
Should I push 'em?

@ezr-ondrej ezr-ondrej merged commit 8d9639c into theforeman:master May 7, 2024
8 checks passed
@ezr-ondrej
Copy link
Member

Thank you @dosas ! 🧡

knoppi pushed a commit to ATIX-AG/foreman that referenced this pull request Aug 9, 2024
- Bump version of ldap_fluff to the next version
- Add netiq to LDAP auth-sources

This PR is a consequence of [Bump version to 0.7.0 theforeman#80](theforeman/ldap_fluff#80) and [Add NetIQ ldap-flavour theforeman#71](theforeman/ldap_fluff#71)
knoppi pushed a commit to ATIX-AG/foreman that referenced this pull request Sep 12, 2024
- Bump version of ldap_fluff to the next version
- Add netiq to LDAP auth-sources

This PR is a consequence of [Bump version to 0.7.0 theforeman#80](theforeman/ldap_fluff#80) and [Add NetIQ ldap-flavour theforeman#71](theforeman/ldap_fluff#71)
sbernhard pushed a commit to theforeman/foreman that referenced this pull request Sep 25, 2024
- Bump version of ldap_fluff to the next version
- Add netiq to LDAP auth-sources

This PR is a consequence of [Bump version to 0.7.0 #80](theforeman/ldap_fluff#80) and [Add NetIQ ldap-flavour #71](theforeman/ldap_fluff#71)
ColeHiggins2 pushed a commit to ColeHiggins2/foreman that referenced this pull request Nov 1, 2024
- Bump version of ldap_fluff to the next version
- Add netiq to LDAP auth-sources

This PR is a consequence of [Bump version to 0.7.0 theforeman#80](theforeman/ldap_fluff#80) and [Add NetIQ ldap-flavour theforeman#71](theforeman/ldap_fluff#71)
ColeHiggins2 pushed a commit to ColeHiggins2/foreman that referenced this pull request Nov 1, 2024
- Bump version of ldap_fluff to the next version
- Add netiq to LDAP auth-sources

This PR is a consequence of [Bump version to 0.7.0 theforeman#80](theforeman/ldap_fluff#80) and [Add NetIQ ldap-flavour theforeman#71](theforeman/ldap_fluff#71)
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.

3 participants