Answers: <p>There is a configuration option named <code>stopUpdatingLabel</code>. With this feature one can add a label to the pr to stop renovate from updating it like so:</p>
  <pre class="lang-json prettyprint-override"><code>{
    &quot;stopUpdatingLabel&quot;: &quot;take-a-break-renovate&quot;
  }
  </code></pre>
  <p>The feature is enabled by default and listens on the label <code>stop-updating</code>.</p>
  <p>It's documented over here:
  <a href="https://docs.renovatebot.com/configuration-options/#stopupdatinglabel" rel="nofollow noreferrer">https://docs.renovatebot.com/configuration-options/#stopupdatinglabel</a></p>
  
Answers: CC BY-SA 4.0
Answers: 2023-03-23T12:49:43.903Z
Answers: 2023-03-23T12:49:43.903Z
Answers: void
Answers: <p>Maybe you could resolve this by pinning the version of the problem library temporarily so it doesn't update it to the &quot;erroring version&quot;?</p>
  <p>You could use the <code>packageRules</code> <a href="https://docs.renovatebot.com/configuration-options/" rel="nofollow noreferrer">configuration</a> to set the allowed version to the known good one, preventing the problematic update.</p>
  <pre class="lang-json prettyprint-override"><code>&quot;packageRules&quot;: [
    {
      &quot;matchPackageNames&quot;: [&quot;@angular/router&quot;],
      &quot;allowedVersions&quot;: &quot;&lt;15.0.0&quot;
    }
  ]
  </code></pre>
  
Answers: CC BY-SA 4.0
Answers: 2023-03-23T11:55:48.727Z
Answers: Yes, indeed a nice workaround but I want to work more stateless, without editing any config. Preferred ways would be to write a comment, change the title or add a specific label to the pr
Answers: void
Answers: CC BY-SA 4.0
Answers: 2023-03-23T13:22:38.987Z
Answers: Another way, if you want to change the config concerning that, would be the "ignoreDeps" option.
Answers: void
Answers: CC BY-SA 4.0
Answers: 2023-03-23T10:48:52.140Z
Answers: 2023-03-23T10:48:52.140Z
Answers: Fenton
Body: <p>We have configured renovate for few of our repositories. It generates PRs after approval via dependency dashboard and automerges patch releases.</p>
  <p>But there is one update which fails the CI - it look like there is an error in the library itself. While we continue to work on the master branch renovate rebases it's update branches which again triggers the CI.</p>
  <p>Can I pause renovate to work on that single PR without closing it until we have have fixed this dependency so that it dos not start the CI  over and over? (It will fail anyway)</p>
  
Tags: <continuous-integration>
Title: Pause renovatebot for single PR
UserDisplayName: void
ThreadText: # Pause renovatebot for single PR
  
  (Asked by: username_0 on 2023-03-23)
  
  We have configured renovate for few of our repositories. It generates PRs after approval via dependency dashboard and automerges patch releases.
  
  But there is one update which fails the CI - it look like there is an error in the library itself. While we continue to work on the master branch renovate rebases it's update branches which again triggers the CI.
  
  Can I pause renovate to work on that single PR without closing it until we have have fixed this dependency so that it dos not start the CI over and over? (It will fail anyway)
  
  **Tags:** continuous-integration
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2023-03-23. Score: 1
  
  There is a configuration option named `stopUpdatingLabel`. With this feature one can add a label to the pr to stop renovate from updating it like so:
  
  ```json
  {
    "stopUpdatingLabel": "take-a-break-renovate"
  }
  
  ```
  
  The feature is enabled by default and listens on the label `stop-updating`.
  
  It's documented over here:
  <https://docs.renovatebot.com/configuration-options/#stopupdatinglabel>
  
  
  ---
  
  ### Answer by username_1 on 2023-03-23. Score: 0
  
  Maybe you could resolve this by pinning the version of the problem library temporarily so it doesn't update it to the "erroring version"?
  
  You could use the `packageRules` [configuration](https://docs.renovatebot.com/configuration-options/) to set the allowed version to the known good one, preventing the problematic update.
  
  ```json
  "packageRules": [
    {
      "matchPackageNames": ["@angular/router"],
      "allowedVersions": "<15.0.0"
    }
  ]
  
  ```
  
  > **Comments:**
  > **username_0**: Yes, indeed a nice workaround but I want to work more stateless, without editing any config. Preferred ways would be to write a comment, change the title or add a specific label to the pr  
  > **username_0**: Another way, if you want to change the config concerning that, would be the "ignoreDeps" option.  
  
  ---
  
  