403 from jitpack maven repo

Resolved 💬 2 comments Opened Oct 14, 2025 by tkachenkoas Closed Nov 10, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

codex cloud

Which model were you using?

_No response_

What platform is your computer?

_No response_

What steps can reproduce the bug?

My Gradle project in Kotlin is using this library

https://github.com/kotlin-telegram-bot/kotlin-telegram-bot

repositories {
    maven { url "https://jitpack.io" }
]


`implementation 'io.github.kotlin-telegram-bot.kotlin-telegram-bot:telegram:6.2.0'`

Build fails for Codex Cloud Agent like this:

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileKotlin'.
> Could not resolve all files for configuration ':compileClasspath'.
   > Could not resolve io.github.kotlin-telegram-bot.kotlin-telegram-bot:telegram:6.2.0.
     Required by:
         project :
      > Could not resolve io.github.kotlin-telegram-bot.kotlin-telegram-bot:telegram:6.2.0.
         > Could not get resource 'https://jitpack.io/io/github/kotlin-telegram-bot/kotlin-telegram-bot/telegram/6.2.0/telegram-
6.2.0.pom'.
            > Could not GET 'https://jitpack.io/io/github/kotlin-telegram-bot/kotlin-telegram-bot/telegram/6.2.0/telegram-6.2.0.
pom'. Received status code 403 from server: Forbidden

It works fine for me locally and on github actions. Is there some issue that Codex Cloud is somehow banned by jitpack? I'm not even sure whether I should report it to jitpack or Codex

What is the expected behavior?

_No response_

What do you see instead?

_No response_

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 10 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #4771

Powered by Codex Action

tkachenkoas · 9 months ago

jitpack is not included in "default" repositories list - need to be explicitly allowed manually