Hello! We are running our annual fundraising. Please consider making a donation if you value this freely available service or want to support people around the world working towards liberatory social change. https://riseup.net/donate.

  1. 15 Dec, 2021 1 commit
  2. 29 Nov, 2021 2 commits
    • georg's avatar
      db: add migration to specify string column limits explicitly · 68151f0d
      georg authored
      It seems, the change to ActiveRecord >= 6.0 makes this necessary.
      Without doing this, the auto-generated database schema file would drop
      these limits, if running migrations.
      
      It seems, this problems has been ongoing since quite some time. For
      details, see [1].
      
      [1] https://github.com/rails/rails/issues/19001
      68151f0d
    • georg's avatar
      db: add migration to change boolean values to integers · 9ee12c4a
      georg authored
      Since ActiveRecord >= 6.0, the SQLite3 connection adapter relies on
      boolean serialization to use 1 and 0, but does not natively recognize
      't' and 'f' as booleans were previously serialized.
      
      Accordingly, this migration handles conversion of both column defaults
      and stored data provided by a user.
      
      In contrast to other migrations, only a 'forward' method is provided, a
      mechanism to 'reverse' is not. Given the nature of this migration, the
      later is not really required.
      
      Unfortunately, we missed this breaking change when bumping ActiveRecord
      to >= 6.0 in Schleuder version 4.0. This caused quite some work
      upstream, but also in downstream environments and, last but not least,
      at the side of users.
      
      We should extend our CI to explicitly test, and ensure things work as
      expected, if running a Schleuder setup in real world. As of now, we
      don't ensure data provided by a user in Schleuder version x still works
      after upgrading to version y.
      
      Closes #505
      9ee12c4a
  3. 23 Nov, 2021 1 commit
  4. 19 Nov, 2021 1 commit
  5. 31 Jul, 2021 1 commit
  6. 27 Jul, 2021 1 commit
  7. 13 Jul, 2021 2 commits
  8. 12 Jul, 2021 1 commit
  9. 10 Jul, 2021 1 commit
  10. 02 Jul, 2021 4 commits
  11. 09 Jun, 2021 3 commits
  12. 08 Jun, 2021 3 commits
  13. 05 Jun, 2021 2 commits
  14. 01 Jun, 2021 6 commits
  15. 27 May, 2021 1 commit
  16. 25 May, 2021 1 commit
    • georg's avatar
      CI: changelog: fetch our repository · 16f11496
      georg authored
      The changelog job requires to fetch the latest state of the repository,
      otherwise the result of this check might not be correct.
      
      Up until now, 'origin' was fetched, which points, by default, to the
      remote repository a local checkout was cloned from, initially.
      
      This works for our repository, but might fail for forks, depending on
      when they were forked and if they were updated in the meantime.
      
      This commit ensures the correct repository is fetched. Besides this, the
      amount of data fetched is limited.
      
      Ref schleuder/schleuder!374
      16f11496
  17. 18 May, 2021 2 commits
  18. 15 May, 2021 1 commit
  19. 24 Mar, 2021 3 commits
  20. 23 Mar, 2021 1 commit
  21. 21 Mar, 2021 1 commit
  22. 08 Mar, 2021 1 commit