Skip to content

Conversation

@jasper-elimity
Copy link
Contributor

No description provided.

@jasper-elimity jasper-elimity self-assigned this Oct 6, 2025
Comment on lines +3 to +9
container: ghcr.io/elimity-com/insights-sdk:18279107697
runs-on: ubuntu-22.04
steps:
- uses: actions/checkout@v4
- run: test -z "$(goarrange run -d)"

black:

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {contents: read}
Comment on lines +29 to +35
container: ghcr.io/elimity-com/insights-sdk:18279107697
runs-on: ubuntu-22.04
steps:
- uses: actions/checkout@v4
- run: npm ci
- run: npx buf lint
- run: buf lint

check:

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {contents: read}
Comment on lines +51 to +57
container: ghcr.io/elimity-com/insights-sdk:18279107697
runs-on: ubuntu-22.04
steps:
- uses: actions/checkout@v4
- run: GOFLAGS='-buildvcs=false' golangci-lint run

isort:

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {contents: read}
Comment on lines +58 to +65
container: ghcr.io/elimity-com/insights-sdk:18279107697
runs-on: ubuntu-22.04
steps:
- uses: actions/checkout@v4
- run: poetry install
- run: poetry run isort -c src

mypy:

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {contents: read}
@jasper-elimity jasper-elimity force-pushed the python-support branch 2 times, most recently from aa7cf9b to 091cc6b Compare October 6, 2025 12:13
Comment on lines +3 to +12
container: ghcr.io/elimity-com/insights-sdk:18279107697
runs-on: ubuntu-22.04
steps:
- uses: actions/checkout@v4
- run: npm ci
- run: npm version --no-git-tag-version ${{ github.event.release.tag_name }}
- run: npx tsc
- run: env NPM_CONFIG_//registry.npmjs.org/:_authToken=${{ secrets.NPM_TOKEN }} npm publish --access public
- run: poetry version $(poetry version -s --dry-run ${{ github.event.release.tag_name }})
- run: POETRY_PYPI_TOKEN_PYPI=${{ secrets.PYPI_TOKEN }} poetry publish --build

Check warning

Code scanning / CodeQL

Workflow does not contain permissions Medium

Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {contents: read}
@jasper-elimity jasper-elimity marked this pull request as ready for review October 6, 2025 12:23
@jasper-elimity jasper-elimity enabled auto-merge (squash) October 6, 2025 12:24
@jasper-elimity jasper-elimity merged commit 56e1501 into main Oct 6, 2025
17 checks passed
@jasper-elimity jasper-elimity deleted the python-support branch October 6, 2025 12:24
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