update license text (arbitrary change so that we can do a new release)

[lukaskollmer]

see title

[codecov]

Codecov Report

Merging #2 (49418d9) into develop (7de65b4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop       #2   +/-   ##
========================================
  Coverage    77.78%   77.78%           
========================================
  Files            6        6           
  Lines           81       81           
========================================
  Hits            63       63           
  Misses          18       18           

Impacted Files	Coverage Δ
Sources/ApodiniDocumentExport/ExportOptions.swift	0.00% <ø> (ø)
...cumentExport/Extensions/Decodable+Extensions.swift	100.00% <ø> (ø)
...cumentExport/Extensions/Encodable+Extensions.swift	100.00% <ø> (ø)
...iDocumentExport/Extensions/String+Extensions.swift	100.00% <ø> (ø)
Sources/ApodiniDocumentExport/FileExtension.swift	78.58% <ø> (ø)
Sources/ApodiniDocumentExport/OutputFormat.swift	100.00% <ø> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7de65b4...49418d9. Read the comment docs.

[lukaskollmer]

@PSchmiedmayer idk what exactly is the issue here, but for some reason SPM will always pick some weird commit which doesn't belong to any branch, instead of simply using the commit associated with the 0.1.1 tag. I had tried to work around this in the past by simply hardcoding the correct commit hash into Apodini's Package.swift file, which actually worked fine for a while, but now seems to have broken.
The idea here is to try to create a new release and hope that SPM will pick that up correctly, so that we don't have to specify the explicit hash in the package file anymore.

[PSchmiedmayer]

@lukaskollmer Thank you, that sounds like a good idea. I have merged the PR and will tag a new release 👍