[BUG] Compilation fails due to a breaking change introduced in `github.com/kataras/golog`

[shaderkill]

Describe the bug
Compilation fails due to a breaking change introduced in github.com/kataras/golog version v0.1.15. The error occurs in the handler_debug.go file of the Iris framework when attempting to use debugLevel.Style as an argument to pio.WriteRich.

To Reproduce
Steps to reproduce the behavior:

1. Use github.com/kataras/golog version v0.1.15 in your project.
2. Attempt to compile a project using github.com/kataras/iris/v12@v12.2.11.
3. Observe the compilation error.

Expected behavior
The project should compile successfully without type mismatch errors between printer.RichOption and pio.RichOption.

Screenshots
Not applicable.

Desktop (please complete the following information):

• OS: [e.g. Windows 10, Ubuntu 22.04]

iris.Version

• v12.2.11

[kataras]

Hello @shaderkill, thanks for opening this issue. Yes, new golog version contains a breaking change but Iris does not uses the v0.1.15, it uses the v0.1.12 which doesn't break things, please verify it at go.mod, maybe you need to re-download Iris?

[bigsk05]

First of all, thank you for your ongoing work on the Iris project.

I would like to share my objective thoughts on the compatibility issue I ran into.

1. What happened
   I follow the common Go community practice of using go get -u to keep dependencies up to date. After a recent update, my project broke because of a breaking change in golog (version v0.1.15 removed pio and made other incompatible changes).

2. Where the problem lies
   golog is also maintained by you. According to Semantic Versioning, any backward-incompatible public API change should be signaled by a major version bump (e.g., v1.0.0 or v2.0.0). While v0 allows some instability, removing a significant dependency like pio is at least a minor-level change (v0.2.0), not a patch/minor release like v0.1.15.

3. How I feel about the response
   In the issue, you suggested that I "downgrade to v0.1.12". As a temporary workaround, that does get the project running again.
   However, as the maintainer of both libraries, I would have expected a different attitude:

Acknowledge that the version management of golog was problematic.

Fix the compatibility proactively, or release an adapted version of Iris.

Not simply blame the user for "not locking the version".

I have been using Go for years, and I have encountered breaking changes in upstream dependencies several times. Almost every maintainer apologised and either reverted the change or published a fix promptly. This is the first time I've been told to "just downgrade and pin". This makes me concerned about the long‑term maintenance quality of this project.

4. My suggestions

Please consider releasing a backward‑compatible patch for golog that restores the removed APIs (at least for a transition period).

Alternatively, if the breaking change is necessary, release it as a v1.0.0 or v0.2.0 following SemVer, and clearly document it in the CHANGELOG.

Also, please understand that developers using go get -u are not doing something wrong – we rely on the reasonable expectation that the ecosystem respects version compatibility conventions.

I still respect the work done on Iris, but I hope this issue can bring more attention to version compatibility discipline. Thank you for reading.