py/objtuple.h · ecc88e949ca5e307d22da4605a40d39ea2df9e3b · TASTE / uPython-mirror

🚨 The deprecated setting “Limit access from this project” for CI_JOB_TOKEN will be removed in GitLab 18.0 by end of May.

💡 What is the CI_JOB_TOKEN?

The CI_JOB_TOKEN is a secure authentication token automatically generated for each job in your CI/CD pipeline. It allows the job to interact with GitLab resources like repositories, artifacts, and APIs — all without needing personal credentials. CI/CD jobs can use this token to access resources in other projects.

🔍 Does This Affect My Projects?

You are impacted if:

Your project currently uses “Limit access from this project” under Settings > CI/CD > Job token permissions.

You have jobs that use CI_JOB_TOKEN to access other GitLab projects.

🧭 To Check Before End of May:

Go to Settings > CI/CD > Job Token Permissions in your project. If “Limit access from this project” is enabled, you need to migrate the same rules to the “Authorized groups and projects” allowlist. Make sure to select "Only this project and any groups and projects in the allowlist".

Blame

Aug 30, 2014
ecc88e94
Change some parts of the core API to use mp_uint_t instead of uint/int. · ecc88e94
Damien George authored Aug 30, 2014
```
Addressing issue #50, still some way to go yet.
```
ecc88e94
Change some parts of the core API to use mp_uint_t instead of uint/int.
Damien George authored Aug 30, 2014
```
Addressing issue #50, still some way to go yet.
```

Provided with ❤️ by esait | 📜 Terms of Service | 📊 Live metrics | Need help? esait.service.desk@esa.int

Admin message