2019-01-08 verison 1.2.6:
* Update Ruby version 2.6 dependency (especially for Windows environment)
* (version 1.2.4 and 1.2.5 were also releases for updated Ruby versions)
## 1.8.0
* Constrain rubocop version to avoid breaking Travis CI builds (05e507f5)
* Avoid calling Kernel#format from ObjectMethods#mocha_inspect - thanks to @hoffmanilya (#345)
* Fix build matrix script (#346)
* Avoid deprecation warning in gemspec (4976e0bc)
* Removed link to documentation translation (ef428ea2)
* Don't use the new bundler v2 in builds (683ded9b)
* Moved documentation from https://gofreerange.com/mocha/docs to https://mocha.jamesmead.org/ [683ded...a17fde](https://github.com/freerange/mocha/compare/683ded...a17fde)
1.10.0 / 2019-01-06
-------------------
Added:
* Add /opt/local/lib/ to ffi's fallback library search path. #638
* Add binary gem support for ruby-2.6 on Windows
* Add FreeBSD on AArch64 and ARM support. #644
* Add FFI::LastError.winapi_error on Windows native or Cygwin. #633
Changed:
* Update to rake-compiler-dock-0.7.0
* Use 64-bit inodes on FreeBSD >= 12. #644
* Switch time_t and suseconds_t types to long on FreeBSD. #627
* Make register_t long_long on 64-bit FreeBSD. #644
* Fix Pointer#write_array_of_type #637
Removed:
* Drop binary gem support for ruby-2.0 and 2.1 on Windows
6.0.15 - 2018-10-31
Added
* (Go) Executables are uploaded to GitHub releases.
Fixed
* Fix bug where leading tabs prevented parser from identifying keywords (#512
[VjacheslavVytjagov])
* [JavaScript] Fix JavaScript build (#499 noisygerman)
6.0.13 - 2018-09-25
This major release aligns Gherkin with Example Mapping, a collaborative
technique for designing scenarios and discovering details about rules and
behaviour.
A new Rule keyword has been introduced, and acts as a grouping of one or more
Examples - a new synonym for Scenario. The Scenario Outline keyword can now
be interchanged with the Scenario keyword, which makes Gherkin a little less
confusing, especially to beginners. These are the first major change to the
Gherkin grammar in 8 years or so, and we're pretty excited about them. We
hope they will guide people towards thinking of scenarios as examples of
business rules rather than a series of form submissions and link clicking.
This rule-focused style engages product owners, and can act as amazing living
documentation of your product. It opens up for the true benefits of BDD - a
business-friendly format for describing and agreeing on software behaviour,
and a guide to development. Developers will code against this spec, and
produce better (simpler) software faster. The software will do what it says
on the tin.
The new Gherkin grammar is backwards compatible, meaning that existing Gherkin
documents are still valid.
The library API however is not backwards compatible. It is now a stream-like
API which produces a stream of messages (source, AST and pickle messages).
Internally, each library shells out to a go executable (embedded in the
library for all major OSes and processor architectures), and communicates via
STDIN/STDOUT using protocol buffers. The rationale behind this architectural
change is to reduce the maintenance burden (a single parser rather than a
dozen), but also to make it quicker and easier to implement a Gherkin library
in a new language. Just generate some protobuf classes/structs and write a
small program that shells out and communicates using those messages.
Our preliminary benchmarks suggest that performance is comparable to the
native implementations, or better. There is a small hit in startup cost, but
this is offset against a higher throughput of the parser.
At the time of this writing Gherkin 6 is nearly integrated in Cucumber-JVM and
Cucumber-Ruby. Integration with Cucumber.js has not started and we would
really welcome some help with that.
The message protocol will continue to evolve to represent runtime information
such as results, parameter types, cucumber expressions and other metadata.
This will make it easier for the community to build plugins for Cucumber. One
HTML Gherkin formatter to rule them all. Statistic plugins and more.
Added
* (TypeScript) - Added TypeScript definitions (.d.ts) for Gherkin.
* Added Rule keyword (#250 aslakhellesoy)
* Added Example as synonym for Scenario in English and many other
languages. This is to align Gherkin with BDD and Example Mapping
terminology. (aslakhellesoy)
* Added Ukoliko as an additional synonym for Given, in Croatian. (#480 banovotz)
Changed
* (JavaScript,Java,Ruby) The native parsers are removed. Parsing is done by
gherkin-go executables which are bundled with the published
libraries. (aslakhellesoy, [jaysonesmith])
* (JavaScript,Java,Ruby,Go) Scenario keyword (or Example keyword) can be used
to create Scenario Outline. (#353 aslakhellesoy)
Removed
* (Java) OSGi support has been removed. (#412 aslakhellesoy)
Fixed
* (JavaScript) Fix ability to pass language to parser. (#401 charlierudolph)
1.2.0:
No changes since the last beta release. Enjoy Waitress!
1.2.0b3:
Bugfixes
- Modified clear_untrusted_proxy_headers to be usable without a
trusted_proxy.
- Modified trusted_proxy_count to error when used without a
trusted_proxy.
1.2.0b2:
Bugfixes
- Fixed logic to no longer warn on writes where the output is required to have
a body but there may not be any data to be written. Solves issue posted on
the Pylons Project mailing list with 1.2.0b1.
1.2.0b1:
Happy New Year!
Features
- Setting the trusted_proxy setting to '*' (wildcard) will allow all
upstreams to be considered trusted proxies, thereby allowing services behind
Cloudflare/ELBs to function correctly whereby there may not be a singular IP
address that requests are received from.
Using this setting is potentially dangerous if your server is also available
from anywhere on the internet, and further protections should be used to lock
down access to Waitress.
- Waitress has increased its support of the X-Forwarded-* headers and includes
Forwarded (RFC7239) support. This may be used to allow proxy servers to
influence the WSGI environment.
This also provides a new security feature when using Waitress behind a proxy
in that it is possible to remove untrusted proxy headers thereby making sure
that downstream WSGI applications don't accidentally use those proxy headers
to make security decisions.
The documentation has more information, see the following new arguments:
- trusted_proxy_count
- trusted_proxy_headers
- clear_untrusted_proxy_headers
- log_untrusted_proxy_headers (useful for debugging)
Be aware that the defaults for these are currently backwards compatible with
older versions of Waitress, this will change in a future release of waitress.
If you expect to need this behaviour please explicitly set these variables in
your configuration, or pin this version of waitress.
Documentation:
https://docs.pylonsproject.org/projects/waitress/en/latest/reverse-proxy.html
- Waitress can now accept a list of sockets that are already pre-bound rather
than creating its own to allow for socket activation. Support for init
systems/other systems that create said activated sockets is not included.
- Server header can be omitted by specifying ident=None or ident=''.
Bugfixes
- Waitress will no longer send Transfer-Encoding or Content-Length for 1xx,
204, or 304 responses, and will completely ignore any message body sent by
the WSGI application, making sure to follow the HTTP standard.
Compatibility
- Waitress has now "vendored" asyncore into itself as waitress.wasyncore.
This is to cope with the eventuality that asyncore will be removed from
the Python standard library in 3.8 or so.
Documentation
- Bring in documentation of paste.translogger from Pyramid. Reorganize and
clean up documentation.
== v1.1.4 [2019-01-08] Michael Granger <ged@FaerieMUD.org>
- Fix PG::BinaryDecoder::Timestamp on 32 bit systems. # 284
- Add new error-codes of PostgreSQL-11.
- Add ruby-2.6 support for Windows fat binary gems and remove ruby-2.0 and 2.1.
19.0:
* Fix string representation of PEP 508 direct URL requirements with markers.
* Better handling of file URLs
This allows for using file:///absolute/path, which was previously
prevented due to the missing netloc.
This allows for all file URLs that urlunparse turns back into the
original URL to be valid.
3.7.3:
Resolved issues
False positive on PSS signatures when externally provided salt is too long.
Include type stub files for Crypto.IO and Crypto.Util.
While here, add a LICENSE definition, and fix compliation on some Linux
distributions.
Change log:
Release blackbox-0.74 released 2018-10-31
-----------------------------------------
Brian Bidulock <bidulock@openss7.org> (9):
update po files
add a release file
remove bashisms from gennews.sh
make autogen.sh handle gnits and remove bashisms
5-part AC_INIT and prefer asciidoc to asciidoctor
generate and distribute release file
add release files to .gitignore
update po files
update release files
Brian Bidulock <bidulock@openss7.com> (1):
Merge pull request #19 from vl-80/fullscreen_fix
VL-80 <vl-80@users.noreply.github.com> (1):
Fix fullscreen mode for non-maximized windows
Release blackbox-0.73 released 2018-05-28
-----------------------------------------
Brian Bidulock <bidulock@openss7.org> (18):
zero errno when not using it
silent rules with /usr prefix
add branch to substitution
add more checks
update make flags
silent now default
tweaks
add some ignores
better build
update install file
initialize XKEYBOARD
update po files
become child subreaper and session leader
Merge branch 'master' of github.com:bbidulock/blackboxwm
prctl is linux-specific
update po files
update release files
update release files
Brian Bidulock <bidulock@openss7.com> (1):
Merge pull request #13 from psolyca/master
Damien Gaignon <damien.gaignon@gmail.com> (1):
Add errno.h as include
