| I've recently reported bug on Xmonad github, they have ### Checklist - [ ] I've read [CONTRIBUTING.md](https://github.com/xmonad/xmonad/blob/master/CONTRIBUTING.md)
- [ ] I tested my configuration with [xmonad-testing](https://github.com/xmonad/xmonad-testing)
I think it is brilliant idea, immediately checked latest git versions, I assume you may add - [ ] I tested my application with [latest stable requirements.txt](...)
And something about triangulation and reporting to another repo too.Sorry to hear about breaks on major version. Ruby gems (libraries) freeze dependencies on major, sometimes minor, example [0]. But applications shipped with Gemfile and Gemfile.lock [1], [2]. So `bundle install` is reproducible [3]: > The presence of a `Gemfile.lock` in a gem's repository ensures that a fresh checkout of the repository uses the exact same set of dependencies every time. We believe this makes repositories more friendly towards new and existing contributors. Ideally, anyone should be able to clone the repo, run `bundle install`, and have passing tests. If you don't check in your `Gemfile.lock`, new contributors can get different versions of your dependencies, and run into failing tests that they don't know how to fix. Yes, docker, msi, Flatpack, AppImage - whatever works for you and your users. It is sad we can't easily statically compile in one file on scripting languages. [0] https://github.com/teamcapybara/capybara/blob/master/capybar... [1] https://github.com/Shopify/example-ruby-app/blob/master/Gemf... [2] https://github.com/Shopify/example-ruby-app/blob/master/Gemf... [3] https://bundler.io/guides/faq.html |