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

fix: doc-test failures #186

Merged
merged 2 commits into from
Aug 21, 2024
Merged

Conversation

CommanderStorm
Copy link
Contributor

@CommanderStorm CommanderStorm commented Aug 21, 2024

@CommanderStorm CommanderStorm changed the title docs: fixed accidental doctest-failiour CI: fixed CI-failiours Aug 21, 2024
@CommanderStorm CommanderStorm changed the title CI: fixed CI-failiours ci: fixed CI-failiours Aug 21, 2024
@DDtKey DDtKey changed the title ci: fixed CI-failiours ci: fix CI-failures Aug 21, 2024
@DDtKey DDtKey changed the title ci: fix CI-failures fix: doc-test failures Aug 21, 2024
@DDtKey
Copy link
Contributor

DDtKey commented Aug 21, 2024

Thanks!
I've updated the title, because it's fix: rather than ci: because we don't change the CI itself

@DDtKey DDtKey merged commit 535e648 into testcontainers:main Aug 21, 2024
5 of 6 checks passed
@CommanderStorm CommanderStorm deleted the zookeeper branch August 21, 2024 02:04
DDtKey pushed a commit that referenced this pull request Aug 21, 2024
In CI, we are currently using `actions-rs` variant of steps. [They are
pretty deprecated.](https://github.com/actions-rs)
This resolves these, which I noticed during #186's [actions
run](https://github.com/testcontainers/testcontainers-rs-modules-community/actions/runs/10481678682?pr=186):


![image](https://github.com/user-attachments/assets/26f6a040-314e-4183-bec9-0b0a03701b32)

There are a ton of options avaliable, maybe even a `rust-lang`-action
rust-lang/rustup#3409
Currently, that is not the case.
(open to alternatives if you prefer another one more ^^)

> [!NOTE]
> This is not without downside as replacing `uses: actions-rs/cargo`
with `run: cargo ...` does not come with the annotations that github
displays f. ex. here from another repo where I recently also contributed
this:
>
![image](https://github.com/user-attachments/assets/6b61c970-800d-4489-8433-bd5df44bc5fa)
> Said annotation would still be shown, but only as a test failour and
not inline..

I have also added the nightly rustfmt part ^^
@github-actions github-actions bot mentioned this pull request Aug 31, 2024
DDtKey pushed a commit that referenced this pull request Aug 31, 2024
## 🤖 New release
* `testcontainers-modules`: 0.9.0 -> 0.10.0

<details><summary><i><b>Changelog</b></i></summary><p>

<blockquote>

## [0.10.0] - 2024-08-31

### Bug Fixes

- Doc-test failures
([#186](#186))

### Documentation

- Added docs for Apache ZooKeeper
([#184](#184))
- Documented all ports which containers at least expose
([#183](#183))
- Enable `rustfmt` for doc comments
([#187](#187))
- Fixed rustfmt violation in the `openldap` module
([#189](#189))
- Fixed a bit of missing docs in the openldap module
([#191](#191))
- Complete the documentation for the meilisearch module
([#192](#192))
- Complete the `*_PORT` documentation
([#195](#195))
- Add `pub mod` docs
([#193](#193))
- Documents the neo4j plugins
([#194](#194))

### Features

- Added an `OpenLDAP` testcontainer module
([#180](#180))
- Add support for `apache\kafka` docker image
([#178](#178))
- [**breaking**] Update `testcontainers` to 0.22.0
([#203](#203))

### Miscellaneous Tasks

- Changed from `actions-rs` to a more maintained CI alternative
([#188](#188))

### Refactor

- [**breaking**] Changed `KAFKA_PORT` to a `ContainerPort`
([#185](#185))

<!-- generated by git-cliff -->
</blockquote>


</p></details>

---
This PR was generated with
[release-plz](https://github.com/MarcoIeni/release-plz/).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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