deploy-queue v0.7.0

[jcgruenhage]

GHA job URL as fallback

We have a job like this everywhere where we use the deploy queue:

- name: Get URL for current job
  id: get-current-job-url
  env:
    GH_TOKEN: ${{ github.token }}
  run: |
    html_url=$(gh api --paginate repos/${GITHUB_REPOSITORY}/actions/runs/${GITHUB_RUN_ID}/jobs \
      --jq '.jobs[] | select(.runner_name =="${{ runner.name }}") | .html_url')
    echo "html-url=$html_url" | tee -a ${GITHUB_OUTPUT}
  if: ${{ vars.DEPLOY_QUEUE_ENABLED == 'true' }}

For job steps, is definitely not necessary, we get the same URL like this:

- run:
    echo "${SERVER_URL}/${REPOSITORY}/actions/runs/${RUN_ID}/job/${CHECK_RUN_ID}"
  env:
    SERVER_URL: ${{ github.server_url }}
    REPOSITORY: ${{ github.repository }}
    RUN_ID: ${{ github.run_id }}
    CHECK_RUN_ID: ${{ job.check_run_id }}

Hoping that composite actions also get access to job.check_run_id, I'm trying to fully inline this.

Small follow-up fixes for #67

• align output of list cells with slack message
• expose list-cells through gh action
• name list cells consistently

Adjustments to github output handling

• support multi-line outputs
• use advisory locks to prevent accidental concurrent writes

Added after flakyness like seen in https://github.com/neondatabase/dev-actions/actions/runs/19367137928/job/55414533340?pr=70 printing things like this:

All tests completed successfully
Error: Unable to process file command 'output' successfully.
Error: Invalid format '6'

Not knowing that this is a concurrency problem and just trying a random thing that came to mind I implemented multi-line output support. This turned it from flaky to always failing, but gave very clear output showing that this is a concurrency issue:

All tests completed successfully
Error: Unable to process file command 'output' successfully.
Error: Invalid value. Matching delimiter not found '<<<<EOFEOFEOF'

Now with the concurrency problem fixed, it's stable again.

Test updates:

• Add compatibility tests that use the action itself for the happy path to ensure basic e2e backwards compatibility
• Run integration tests of older versions against the new schema to ensure query compatibility

I'm adding both because the compatibility problem between 0.5.1 and 0.6.0 with missing migrations being treated as a critical problem would not have been caught by the latter, while most more nuanced query-level problems would not be caught by the former.

[bayandin]

Reviewed the workflow part — nice!
And added a question, if everything is fine — LGTM

[jcgruenhage]

Only new changes are the newly introduced compatibility tests and the matrix strategy for the integration tests, the rest remained unchanged:

❯ git range-diff 781f934..44b0c6d 781f934..4e51c782
 1:  4734560 =  1:  4734560 impr(deploy-queue): use GHA job URL as fallback
 2:  6c99e77 =  2:  6c99e77 fix(deploy-queue): name `list cells` consistently
 3:  adadde0 =  3:  adadde0 fix(deploy-queue): expose `list-cells` through gh action
 4:  f460f8f =  4:  f460f8f fix(deploy-queue): align output of `list cells` with slack message
 5:  f8d2320 =  5:  f8d2320 chore(deploy-queue): don't set URL for e2e tests
 6:  f3aec19 =  6:  f3aec19 fix(deploy-queue): support multi-line github outputs
 7:  4afb423 =  7:  4afb423 fix(deploy-queue): exclusive advisory locks for writes to GITHUB_OUTPUT
 8:  667efa1 =  8:  667efa1 fix(deploy-queue): allow running with missing migrations
 -:  ------- >  9:  7f03960 impr(deploy-queue): test old and new versions against same database
 -:  ------- > 10:  0817dd6 impr(deploy-queue): run integration tests against newer schema
 9:  44b0c6d = 11:  4e51c78 chore(deploy-queue): bump version to 0.7.0

[jcgruenhage]

And as expected, testing against 0.5.1 failed because 0.5.1 refuses to work when there are unknown migrations applied to the database. See https://github.com/neondatabase/dev-actions/actions/runs/19466750059/job/55703743925.

I've removed the test for 0.5.1, but we'll have to make sure nothing is referencing 0.5.1 anymore before we can update to >=0.6.0. We've got 0.5.2 as an intermediate release to help with that.

[Shugenya]

Looks good!
I guess this means we can finally get rid of the "Get URL for current job" step