Skip to content
This repository has been archived by the owner on Apr 4, 2023. It is now read-only.

Releases: eregs/regulations-parser

4.3.1

06 Jul 15:08
Compare
Choose a tag to compare

Bug Fixes

  • #367, #371 Fix bug around appendix title processing
  • #373 Pin dependencies
  • #375 Pin FEC integration tests
  • #378 Avoid explosions when amendment parsing fails
  • #376 Fix packaging details

4.3.0

03 Apr 00:29
Compare
Choose a tag to compare

New Features

  • #351 Add command for full-issuance/reissuance notices

Bugfixes/Refactors

  • #344, #349 Continue breaking out CFPB-specific interpretation functions
  • #346 Add additional flake8 plugins
  • #352 Fix for Python2 support
  • #353 Fixes for EPA integration tests
  • #354 Use volume/page # rather than publication date when sorting versions
  • #357 Bugfixes around parsing Subparts in notices
  • #359 Skip notices which don't have XML
  • #359 Account for empty P's in dates; different title tag in appendix
  • #363 Remove deprecated parameter on eregs clear
  • #362 Fix docker build

4.2.0

31 Dec 16:39
Compare
Choose a tag to compare

Quarterly release, including refactors and a new command.

  • #338 adds more documentation around our extension (a.k.a. plugin) points
  • #339 moves the integration suite test files into this repo (rather than in an S3 bucket)
  • #343 adds a new command to derive paragraph depths from the command line
  • #341 and #342 begin the work of separating interpretations (a largely CFPB-specific feature) into its own module.

4.1.0

02 Dec 22:46
Compare
Choose a tag to compare

Bugfix and cleanup release

  • Account for notices without effective dates #330
  • Skip final rules issued before the first annual edition #330
  • Change notice page number storage #330
  • Bugfix: #323 Use a tmpdir for file upload storage
  • Bugfix: #324 Account for E tags in subpart/subject group titles
  • Tech debt: #329 Use test data from this repo rather than s3
  • Tech debt: #333 Standardize the tagged_text attribute
  • Tech debt: Misc refactors/cleanups #319, #325, #326, #328, #330, #332, #334

4.0.0

13 Oct 19:48
Compare
Choose a tag to compare

This is a relatively arbitrary distinction, but we want to be more consistent
about out version numbers to make downstream builds more consistent. As noted,
somewhat arbitrary, but let's say

1.0.0 built the data based on plain text input files
2.0.0 used XML and the Federal Register as input
3.0.0 switched to using annual editions as much as possible and broke apart
the build process into several sub-tasks
4.0.0 begins the work of running the parser as a web service