Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not execute npm publish in GitHub Actions when package version is not changed #89

Open
Konard opened this issue Jan 24, 2024 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@Konard
Copy link
Member

Konard commented Jan 24, 2024

Run npm publish
npm notice 
npm notice 📦  @deep-foundation/npm-packager@0.0.40
npm notice === Tarball Contents === 
npm notice 937B   .github/workflows/main.yml     
npm notice 196B   .github/workflows/npm-build.yml
npm notice 27B    .gitpod.yml                    
npm notice 1.2kB  LICENSE                        
npm notice 411B   README.md                      
npm notice 522B   automation/build.ts            
npm notice 436B   config.json                    
npm notice 23.8kB deep.json                      
npm notice 21.8kB diff/core-1.json               
npm notice 21.9kB diff/core-2.json               
npm notice 20.3kB diff/core.json                 
npm notice 11.6kB handlers/install-code.ts       
npm notice 9.1kB  handlers/publish-code.ts       
npm notice 956B   package.json                   
npm notice 6.8kB  src/npm-packager-proxy.ts      
npm notice 10.9kB test.ts                        
npm notice 563B   tsconfig.json                  
npm notice === Tarball Details === 
npm notice name:          @deep-foundation/npm-packager           
npm notice version:       0.0.40                                  
npm notice filename:      deep-foundation-npm-packager-0.0.40.tgz 
npm notice package size:  17.1 kB                                 
npm notice unpacked size: 131.4 kB                                
npm notice shasum:        468ab33ff11584c61adc29045d1a844f224d1f93
npm notice integrity:     sha512-/goTCSYL8NPPM[...]Ns0Syc31N2ntg==
npm notice total files:   17                                      
npm notice 
npm notice Publishing to https://registry.npmjs.org/ with tag latest and default access
npm ERR! code E403
npm ERR! 403 403 Forbidden - PUT https://registry.npmjs.org/@deep-foundation%2fnpm-packager - You cannot publish over the previously published versions: 0.0.40.
npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! 403 a package version that is forbidden by your security policy, or
npm ERR! 403 on a server you do not have access to.

npm ERR! A complete log of this run can be found in: /home/runner/.npm/_logs/2024-01-24T22_56_24_346Z-debug-0.log
Error: Process completed with exit code 1.

https://github.com/deep-foundation/npm-packager/actions/runs/7647287654/job/20837913972#step:6:1

@Konard Konard added the bug Something isn't working label Jan 24, 2024
@Konard
Copy link
Member Author

Konard commented Mar 24, 2024

Screenshot_20240324_231436

Now it looks like this.

@Konard
Copy link
Member Author

Konard commented Mar 24, 2024

@FreePhoenix888 can you help fix this issue? I think you should have enough context on how it works in other repositories.

@FreePhoenix888
Copy link
Member

FreePhoenix888 commented Mar 25, 2024

@FreePhoenix888 can you help fix this issue? I think you should have enough context on how it works in other repositories.

I have added https://github.com/deep-foundation/deeplinks/blob/main/.github/workflows/npm-publish.yml workflow.

I also gave it a try: https://github.com/deep-foundation/npm-packager/actions/runs/8416323689
And it works. We can remove the old main.yml and close this issue now. What do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Todo
Development

No branches or pull requests

2 participants