Skip to content

Conversation

@Deniallugo
Copy link
Contributor

@Deniallugo Deniallugo commented Jun 19, 2025

What ❔

Release zksync os prover and server. For using it later in demo stands.

Why ❔

Is this a breaking change?

  • Yes
  • No

Operational changes

Checklist

  • PR title corresponds to the body of PR (we generate changelog entries from PRs).
  • Tests for the changes have been added / updated.
  • Documentation comments have been added / updated.
  • Code has been formatted via zkstack dev fmt and zkstack dev lint.

@Deniallugo Deniallugo changed the base branch from main to zksync-os-integration June 19, 2025 14:52
@github-actions
Copy link
Contributor

github-actions bot commented Jun 19, 2025

Hey there! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.
Examples of valid PR titles:

  • feat(eth_sender): Support new transaction type
  • fix(state_keeper): Correctly handle edge case
  • ci: Add new workflow for linting

Details:

No release type found in pull request title "release zksync os". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

Comment on lines 13 to 42
runs-on: ubuntu-latest
name: Test changed-files
outputs:
core: ${{ steps.changed-files-yaml.outputs.core_any_changed }}
prover: ${{ steps.changed-files-yaml.outputs.prover_any_changed }}
all: ${{ steps.changed-files-yaml.outputs.all_any_changed }}
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4
with:
fetch-depth: 2

- name: Get all test, doc and src files that have changed
id: changed-files-yaml
uses: tj-actions/changed-files@48566bbcc22ceb7c5809ebdd27377309f2c3de8c # v39
with:
files_yaml: |
# TODO: make it more granular, as already implemented in CI workflow
# We don't want to be rebuilding and redeploying all the Docker images when eg. only document have changed
prover:
- prover/**
- core/lib/**
- zkos_prover/**
- '!core/lib/zksync_core_leftovers/**'
core:
- core/**
all:
- '!core/**'
- '!prover/**'
setup:

Check warning

Code scanning / CodeQL

Workflow does not contain permissions

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 24 to 42
- name: Get all test, doc and src files that have changed
id: changed-files-yaml
uses: tj-actions/changed-files@48566bbcc22ceb7c5809ebdd27377309f2c3de8c # v39
with:
files_yaml: |
# TODO: make it more granular, as already implemented in CI workflow
# We don't want to be rebuilding and redeploying all the Docker images when eg. only document have changed
prover:
- prover/**
- core/lib/**
- zkos_prover/**
- '!core/lib/zksync_core_leftovers/**'
core:
- core/**
all:
- '!core/**'
- '!prover/**'
setup:

Check failure

Code scanning / CodeQL

Use of a known vulnerable action

The workflow is using a known vulnerable version ([48566bbcc22ceb7c5809ebdd27377309f2c3de8c](1)) of the [tj-actions/changed-files](2) action. Update it to [41](3)
Comment on lines 42 to 63
name: Setup
runs-on: [ matterlabs-deployer-stage ]
outputs:
image_tag_suffix: ${{ steps.generate-tag-suffix.outputs.image_tag_suffix }}
prover_fri_gpu_key_id: ${{ steps.extract-prover-fri-setup-key-ids.outputs.gpu_short_commit_sha }}
steps:
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4

- name: Generate image tag suffix
id: generate-tag-suffix
run: |
sha=$(git rev-parse --short HEAD)
ts=$(date +%s%N | cut -b1-13)
echo "image_tag_suffix=${sha}-${ts}" >> $GITHUB_OUTPUT

- name: Generate outputs with Prover FRI setup data keys IDs
id: extract-prover-fri-setup-key-ids
run: |
./prover/extract-setup-data-keys.sh >> $GITHUB_OUTPUT

build-push-core-images:

Check warning

Code scanning / CodeQL

Workflow does not contain permissions

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 63 to 76
name: Build and push images
needs: [ setup, changed_files ]
uses: ./.github/workflows/build-core-template.yml
if: needs.changed_files.outputs.core == 'true' || needs.changed_files.outputs.all == 'true'
with:
image_tag_suffix: ${{ needs.setup.outputs.image_tag_suffix }}
action: "build"
secrets:
DOCKERHUB_USER: ${{ secrets.DOCKERHUB_USER }}
DOCKERHUB_TOKEN: ${{ secrets.DOCKERHUB_TOKEN }}


build-push-prover-images:

Check warning

Code scanning / CodeQL

Workflow does not contain permissions

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: {{}}
Comment on lines 76 to 87
name: Build and push images
needs: [ setup, changed_files ]
uses: ./.github/workflows/build-zksyncos-prover-template.yml
if: needs.changed_files.outputs.prover == 'true' || needs.changed_files.outputs.all == 'true'
with:
image_tag_suffix: ${{ needs.setup.outputs.image_tag_suffix }}
ERA_BELLMAN_CUDA_RELEASE: ${{ vars.ERA_BELLMAN_CUDA_RELEASE }}
action: "build"
secrets:
DOCKERHUB_USER: ${{ secrets.DOCKERHUB_USER }}
DOCKERHUB_TOKEN: ${{ secrets.DOCKERHUB_TOKEN }}

Check warning

Code scanning / CodeQL

Workflow does not contain permissions

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: {{}}
@Deniallugo Deniallugo force-pushed the deniallugo-release-zksync-os branch from fbbcad0 to b007d1e Compare June 19, 2025 16:02
@Deniallugo Deniallugo force-pushed the deniallugo-release-zksync-os branch from e74cc9c to ba77cdb Compare June 20, 2025 08:33
Signed-off-by: Danil <[email protected]>
Signed-off-by: Danil <[email protected]>
Signed-off-by: Danil <[email protected]>
Signed-off-by: Danil <[email protected]>
@Deniallugo Deniallugo force-pushed the deniallugo-release-zksync-os branch from 83287c0 to d767281 Compare June 20, 2025 10:48
Signed-off-by: Danil <[email protected]>
Signed-off-by: Danil <[email protected]>
@Deniallugo Deniallugo force-pushed the deniallugo-release-zksync-os branch 2 times, most recently from 9452136 to ac2a555 Compare June 23, 2025 14:07
@Deniallugo Deniallugo force-pushed the deniallugo-release-zksync-os branch from ac2a555 to 5ddeea8 Compare June 23, 2025 14:45
Signed-off-by: Danil <[email protected]>
Signed-off-by: Danil <[email protected]>
@Deniallugo Deniallugo force-pushed the deniallugo-release-zksync-os branch from 44a749f to 75e2861 Compare June 23, 2025 16:36
Signed-off-by: Danil <[email protected]>
Signed-off-by: Danil <[email protected]>
@Deniallugo Deniallugo force-pushed the deniallugo-release-zksync-os branch from 56b6cc2 to 1734b22 Compare June 23, 2025 17:07
Signed-off-by: Danil <[email protected]>
Signed-off-by: Danil <[email protected]>
@Deniallugo Deniallugo marked this pull request as ready for review June 24, 2025 11:38
@Deniallugo Deniallugo requested a review from a team as a code owner June 24, 2025 11:38
@Deniallugo Deniallugo requested review from alexandrst88, hatemosphere, iluwaa, onyxet, otani88 and yorik and removed request for a team June 24, 2025 11:38
@Deniallugo Deniallugo merged commit 14fc751 into zksync-os-integration Jun 24, 2025
7 of 15 checks passed
@Deniallugo Deniallugo deleted the deniallugo-release-zksync-os branch June 24, 2025 11:38
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.

3 participants