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

OTP 27: bump katana_code from 2.1.0 to 2.1.1 #225

Merged
merged 3 commits into from
Jul 8, 2024
Merged

OTP 27: bump katana_code from 2.1.0 to 2.1.1 #225

merged 3 commits into from
Jul 8, 2024

Conversation

paulo-ferraz-oliveira
Copy link
Contributor

No description provided.

@paulo-ferraz-oliveira
Copy link
Contributor Author

@elbrujohalcon, I can't add reviewers to this, so I'm 👋ing here.

After this, if possible, I'd request a release. Thanks.

This would otherwise break with all the unknown types
and function calls to `rebar3`
@paulo-ferraz-oliveira
Copy link
Contributor Author

I had to push a minor update to rebar.config to prevent breakage on compilation. Other than that, if approved+merged, it should be good for release(GitHub)+publish(Hex.pm).

@paulo-ferraz-oliveira
Copy link
Contributor Author

You might have to tweak the Settings for this: build (25.2.1, 3.20.0) Expected — Waiting for status to be reported, since I changed the target OTP version.

@elbrujohalcon elbrujohalcon merged commit 3e4b2b9 into AdRoll:main Jul 8, 2024
4 checks passed
@elbrujohalcon
Copy link
Collaborator

https://hex.pm/packages/rebar3_hank/1.4.1

@paulo-ferraz-oliveira paulo-ferraz-oliveira deleted the chore/bump-katana_code-lock branch July 8, 2024 19:43
@paulo-ferraz-oliveira
Copy link
Contributor Author

Perfect stuff. Thanks.

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