Depfu

@escapedcat Ok, so this case we didn't find the Github repo since there is no repository field in the package.json. I've fixed it manually now, so it should start working for the next PRs as the tags etc look correct. #repository" target="_blank" rel="nofollow noopener">docs.npmjs.com/cli/v9/configu…

@depfu thanks! github.com/aaronbarnardso…

@depfu "Sorry, we couldn't find anything useful about this release." what is depfu looking for in i.e. github? tags/releases with version number/named releases/changelog file?

@acr__ Hi Alex, would you mind emailing us at hi@depfu.com with the repo this is happening in. Then we’ll have a look.

@depfu We have a yarn workspace monorepo that has missed its weekly scheduled update, and all attempts to manually create a PR via the dashboard don't work. Any tips? Can DM repo & any more info needed.

@benediktdeicke There is, if the projects release all at once with synced version numbers. That's our limitation at the moment. If you have examples for me where these conditions are met, I can add them to our config. (jan)

@depfu Is there a way to “group” related gems together so they always get updated together in one pull request? Similar to how it works with rails, but for others like flipper or rails-autoscale.

Note for our Elixir users: Hex 2.0 has been published and we had to make a couple of small adjustments to adapt to the new resolver and its new error messages - We'll upgrade asap and that will hopefully make dependency resolution much more stable.

Our co-founder @halfbyte is at #euruko2022 and would love to talk to you. He also has a couple of stickers with him.

To whom it may concern: Due to the immediate yank of rails-i18n 7.0.4 and the way we update rails, we've messed up some of the rails 7.0.4 updates. This has now been cleaned up, make sure you update rails-i18n as well, though.

🚀 You can now configure the behavior of Depfu by adding a config file to your repo. Finally! depfu.com/blog/configure…

🚀 Depfu now supports Yarn 3, with a few caveats. depfu.com/blog/yarn-3-su…

@Benoit_Tgt Generally speaking: No. What specific API functionality would you be looking for?

@JorgeOrtega 👍

Yarn Berry support is probably missing a couple of things right now beyond those two caveats - Please let us know if you run into anything. (Let's see how many "interesting" issues will be caused by the plugin system, for example)

Yarn 3 has command line support for tools like Depfu in form of the mode switch. While building Yarn 2 support would be technically possible, it seemes wasteful and upgrading should not be a huge problem for most teams.

So, Yarn Berry support on Depfu is now available, with two important caveats (thread): 1) Depfu will not update the offline cache and 2) Only Yarn 3.x+ is supported. Offline cache support is difficult for us to do - If you need it, you'd need a CI job that updates it.

@MortiK Actually been working on it for a couple of days but it still needs additional testing - First version will also not directly support offline cache maintenance. ETA is "before the end of the year", hopefully. If you want to betatest, drop us an email, please.

@depfu is there an ETA on when depfu will support Yarn 2.x?

@mentalizer @tmcw Thanks for mentioning us! Yeah, we do group updates for scoped packages, if we know about the group (not all scoped packages are updated in lockstep) and if they share a common version number. We also do batching and you can additionally scope the batched updates to dev deps.

@tmcw Pretty sure @depfu does this, at least to some degree

@benediktdeicke This should be fixed now. Please let us know if you still see any weirdness.

@depfu How’s the “merge” command supposed to work? From the description, I assumed it’ll automatically merge the PR once the tests pass, but for some reason that didn’t happen. Posting the command again also seems to have triggered a rebase…? 🧐

@benediktdeicke That’s exactly how it’s supposed to work 😊, but it looks like we don’t handle `skipped` status checks correctly. We’ll fix that.

We're also seeing occasional update failures due to the yanked gem versions, but we should now be able to issue the upgrades to mimemagic to fix that. Please have a closer look at this if you run a rails app in production.

Just a quick heads up: Depfu will eventually roll out updates for the rubygem mimemagic to either 0.3.8 or 0.4.1 but this requires the installation of external dependencies prior to "bundle install". More info: #dependencies" target="_blank" rel="nofollow noopener">github.com/mimemagicrb/mi….