1
0
mirror of https://github.com/e621ng/dtext_rb.git synced 2025-03-04 03:03:03 -05:00

Regenerate dtext.cpp and bump version

This commit is contained in:
Earlopain 2023-04-03 13:40:33 +02:00
parent efc5e6c0e5
commit d01befd873
No known key found for this signature in database
GPG Key ID: 6CFB948E15246897
5 changed files with 8969 additions and 7910 deletions

View File

@ -1,7 +1,7 @@
PATH
remote: .
specs:
dtext_rb (1.10.21)
dtext_rb (1.11.0)
GEM
remote: https://rubygems.org/

View File

@ -10,7 +10,7 @@ There's a `docker-compose.yml` which you can use to quickly run the most common
## Releasing a new version for usage in e621
Commit the changes to `dtext.rl` and the resuling changes in `dtext.c`. Bump the version number in `dtext_rb.gemspec` and `VERSION`. After that is all done you can `bundle lock` in the e6 repository. It should pick up on the increased version.
Commit the changes to `dtext.cpp.rl` and the resuling changes in `dtext.cpp`. Bump the version number in `lib/dtext/version.rb`. After that is all done you can `bundle lock` in the e6 repository. It should pick up on the increased version.
To test these changes locally commit them and update the `Gemfile`s dtext entry. Specifying the commit hash allows you to rebuild the container without having to also increment the version number every time. Don't forget to `bundle lock` before rebuilding.
`gem "dtext_rb", git: "https://github.com/YOUR_FORK/dtext_rb.git", ref: "YOUR_COMMIT_HASH"`

File diff suppressed because it is too large Load Diff

8966
ext/dtext/dtext.cpp Normal file

File diff suppressed because it is too large Load Diff

View File

@ -1,5 +1,5 @@
# frozen_string_literal: true
class DText
VERSION = "1.10.21"
VERSION = "1.11.0"
end