einaregilsson / build-number Goto Github PK

The readme example should have a needs: job1 line in the definition for job2, otherwise job2 can start executing before the job1 artifact has been uploaded and fail

I need the default build number to start at 0, not 1. I think it's worth adding a separate input for this. I can prepare a PR if needed.
In addition, it will also simplify the Use case with a start number.

Warning: The set-env command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

I need the ability to get build number without generating a new one.
Cause:
I am trying to create an auto versioning system based on Conventional Commits and your generator. Each breaking change commit will create a new Major version, each feat: commit will create a new Minor version and each fix: will create a Build version, where the final version will look like Major.Minor.Build.

When using this action, GitHub Actions displays the following warning:

Warning: The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Can this action be updated to prevent any issues when the set-output command is disabled?

We're considering using your action (great work, btw), but it would be useful if the build-number prefix wasn't hardcoded. Appreciate that you can add another prefix, but two seems unnecessary. We could either remove the build-number string altogether, or have the custom prefix override the build-number string? What are your thoughts?

When using this action, GitHub Actions displays the following warning:

Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: einaregilsson/build-number@v3

Can this action be updated to Node 16 to prevent any possible issues when the change to Node 16 is forced?

Suddenly getting this error,

Error: Failed to create new build-number ref. Status: 403, err: null, result: {"message":"Resource not accessible by integration","documentation_url":"https://docs.github.com/rest/reference/git#create-a-reference"}

Hi,
since couple of months (maybe since I upgraded to V3?) I have the following issue:
The script fails, because there are too many "build-number-xxx" tags.
Then I delete all tags, but the latest. I re-run GitHub actions and everything works fine.
But somehow after sometimes all old "build-number-xxx" tags re-appear and the script fails again.
Any idea what is the problem and from were the old tags are re-created?

current plugin saves build number to BUILD_NUMBER/BUILD_NUMBER file. I would like to have it clean and pass between jobs with artefacts (it might be better option as default as well)

please add option for that

current workaround - add BUILD_NUMBER to git ignore

When using runs-on: windows-latest, and this code

echo Build number is $BUILD_NUMBER

I get this:

I could only solve this by using the id: buildnumber, like:

steps:
    - name: Generate build number
      uses: einaregilsson/build-number@v1
      id: buildnumber
      with:
        token: ${{secrets.github_token}}   
    
    - name: Print new build number
      run: echo "Build number is ${{ steps.buildnumber.outputs.build_number }}"

Is this a known issue? And maybe update your readme?

How to reset the build numbers on monthly basis.

If two builds run at the same time they both can get the same build number. I've had this happen a few times.

Hello. Thank you for your work and this script.
But how can i use this variable? I mean i want to put this build.version into file?

Thank you.

Run einaregilsson/build-number@v2
events.js:187
throw er; // Unhandled 'error' event
^

Error: getaddrinfo EAI_AGAIN api.github.com
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:60:26)
Emitted 'error' event on ClientRequest instance at:
at TLSSocket.socketErrorListener (_http_client.js:406:9)
at TLSSocket.emit (events.js:210:5)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
errno: 'EAI_AGAIN',
code: 'EAI_AGAIN',
syscall: 'getaddrinfo',
hostname: 'api.github.com'
}
##[error]Node run failed with exit code 1