Giter Club home page Giter Club logo

semantic-release-python's Issues

Object.hasOwn is not a function Bug

  • I'm submitting a ...
    [x] bug report
    [ ] feature request
    [ ] question about the decisions made in the repository
    [ ] question about how to use this project

Description

Essentially the plugin fails to after the verification step with Object.hasOwn is not a function.

Other information** (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)

Error Log

[8:09:06 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "semantic-release-python"
[8:09:06 PM] [semantic-release] › ✖  Failed step "verifyConditions" of plugin "semantic-release-python"
[8:09:06 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "@semantic-release/exec"
[8:09:06 PM] [semantic-release] › ✔  Completed step "verifyConditions" of plugin "@semantic-release/exec"
[8:09:06 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "@semantic-release/changelog"
[8:09:06 PM] [semantic-release] › ✔  Completed step "verifyConditions" of plugin "@semantic-release/changelog"
[8:09:06 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "@semantic-release/git"
[8:09:06 PM] [semantic-release] › ✔  Completed step "verifyConditions" of plugin "@semantic-release/git"
[8:09:06 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "@semantic-release/gitlab"
[8:09:06 PM] [semantic-release] [@semantic-release/gitlab] › ℹ  Verify GitLab authentication (https://gitlab.com/api/v4)
[8:09:06 PM] [semantic-release] › ✔  Completed step "verifyConditions" of plugin "@semantic-release/gitlab"
[8:09:06 PM] [semantic-release] › ✖  An error occurred while running semantic-release: TypeError: Object.hasOwn is not a function
    at getOption (/builds/lmco/hoppr/hoppr/node_modules/semantic-release-python/lib/util.js:10:17)
    at verifyPoetry (/builds/lmco/hoppr/hoppr/node_modules/semantic-release-python/lib/verify.js:123:23)
    at verify (/builds/lmco/hoppr/hoppr/node_modules/semantic-release-python/lib/verify.js:149:11)
    at validator (/opt/node_modules/semantic-release/lib/plugins/normalize.js:34:30)
    at /opt/node_modules/semantic-release/lib/plugins/pipeline.js:37:40
    at next (/opt/node_modules/p-reduce/index.js:17:9)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  pluginName: 'semantic-release-python'
}
AggregateError: 
    TypeError: Object.hasOwn is not a function
        at getOption (/builds/lmco/hoppr/hoppr/node_modules/semantic-release-python/lib/util.js:10:17)
        at verifyPoetry (/builds/lmco/hoppr/hoppr/node_modules/semantic-release-python/lib/verify.js:123:23)
        at verify (/builds/lmco/hoppr/hoppr/node_modules/semantic-release-python/lib/verify.js:149:11)
        at validator (/opt/node_modules/semantic-release/lib/plugins/normalize.js:34:30)
        at /opt/node_modules/semantic-release/lib/plugins/pipeline.js:37:40
        at next (/opt/node_modules/p-reduce/index.js:17:9)
        at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at /opt/node_modules/semantic-release/lib/plugins/pipeline.js:54:11
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Object.pluginsConf.<computed> [as verifyConditions] (/opt/node_modules/semantic-release/lib/plugins/index.js:80:11)
    at async run (/opt/node_modules/semantic-release/index.js:95:3)
    at async module.exports (/opt/node_modules/semantic-release/index.js:260:22)
    at async module.exports (/opt/node_modules/semantic-release/cli.js:55:5)

Poetry publish throws same error as poetry config

❔ What are you experiencing an issue with?

Latest Release

❔ Version

v2.5.30

🐞 Description

The poetry publish catch block in publishPoetry throws the same error message as the poetry config:

throw new Error(`Failed to run "poetry config repositories.repo ${repoUrl}"`)

This makes it harder to figure out which of the two commands failed. Could the second error thrown be something like:

throw new Error(Failed to run "poetry publish --build --repository --repo")

⏺️ Steps To Reproduce

Set PYPI_TOKEN to an invalid token. Run the publish step and observe the error message.

📒 Relevant Log Output

No response

💡 Possible Solution

throw new Error(Failed to run "poetry publish --build --repository --repo")

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.