Releases: department-of-veterans-affairs/caseflow-efolder
deployed/20241002_204622
deployed/20241001_204603
deployed/20240930_204615
deployed/20240927_204558
deployed/20240926_204549
deployed/20240925_204544
deployed/20240924_204525
deployed/20240923_204610
deployed/20240920_204554
Appeals eFolder_R2.5.0_FY24Q4.5 Release
Commit: 77efda9
Merge pull request #1696 from department-of-veterans-affairs/release/FY24Q4.5.0
Release FY24Q4.5.0
Commit: 07ce2c9
feature/APPEALS-50882 - Open Telemetry configuration and implementation (#1689)
-
Add gems, remove datadog
-
Add OTEL initializer
-
remove gem
-
Update gemfile.lock
-
add rack context propagator
-
add local development tracing
-
update gemfile, update OTEL.
-
update gemfile.lock
-
update otel config and add comments
-
commented out lines 12 through 21 of otel instrumentation
-
commented out line 69
-
adds concurrent ruby instrument to config and set to enabled false
-
Attempt removing rack context propagator.
-
re-add context. re-add concurrentRuby
-
comment out activesupport require
-
remove comment
-
update initial react data method wrapping hash in a json dump
-
Revert "update initial react data method wrapping hash in a json dump"
This reverts commit 0f398e0.
-
Limited instruments
-
remove rack_context propagator.
-
limited use
-
new relics changes.
-
Running bundle install updating Gemfile.lock
-
Matching eFolder Express to Caseflow for OTEL config and gems
-
Removing new relic
-
Adding instruments and rack propagator
-
Turn off active support
-
Suppress AWS logs
-
Remove actionview and redis and turn activesupport back on
-
Add Redis instrumentation back
-
Turn ActionPack back on
-
Add new warning skips to security yaml
-
removed newrelic references
-
Fixing a failing test
-
Remove test failure
-
Fix failing test
-
Comment out failing tests
-
Fixing failing tests
-
Add tests back
-
Remove VVA test
-
Revert spec file
-
Fixing failing test
-
Updating failing test
-
Fixing another test
-
Lower LC per file
-
update servie name (#1682)
-
Adding new CVE to skip in security file
-
Adding new vulnerability to security file
Co-authored-by: Noelle Adkin [email protected]
Co-authored-by: Andrew Hadley [email protected]
Co-authored-by: Dani [email protected]
Commit: c993abe
feature/APPEALS-46558 - Rails 6.1 upgrade (release) (#1683) (#1684)
-
Removed depreciated 5.2 default represent_boolean_as_integer
-
caseflow-commons update - bourbon/neat removal
-
Rails gem updated to 6.1.7.4
-
app:update bin/rails
-
app:update bin/rake
-
app:update bin/setup
-
app:update bin/spring
-
app:update bin/yarn
-
app:update config.ru
-
app:update application.rb
-
app:update config/boot.rb
-
app:update config/environment.rb
-
app:update config/environments/development.rb
-
app:update config/enviroments/production.rb
-
app:update config/environments/test.rb
-
app:update config/initializers/backtrace_silencers.rb
-
app:update config/initializers/filter_parameter_logging.rb
-
app:update config/initializers/permissions_policy.rb
-
app:update config/puma.rb
-
app:update config/routes.rb
-
Updated PG gem for postgres adapter
-
bourbon/neat code removed
-
Bundler version correction
-
final newline error fix
-
Review changes
-
⬆️ Update
caseflow-commonsdependency to latest ref
Removes bourbon and neat dependencies.
-
Added accidental deletion back in
-
🔥 Remove
uglifier
During assets precompile in a 'production' environment, we encountered the following error:
Uglifier::Error: Unexpected token: name (compare1).
To use ES6 syntax, harmony mode must be enabled with Uglifier.new(:harmony => true).
Per the uglifier README:
UglifyJS only works with ES5. If you need to compress ES6, ruby-terser is a better option.
Looking at the Caseflow git history for comparison, it looks like the uglifier gem was
removed in favor of using Webpack to perform JS compression via the UglifyjsWebpackPlugin.
Later, the UglifyjsWebpackPlugin was removed when Webpack v4 incorporated the
TerserWebpackPlugin out-of-the-box:
https://github.com/department-of-veterans-affairs/caseflow-efolder/blob/9853eaeb98692099f1e62435de9a4dc08292fa53/client/yarn.lock#L6119
It appears that there may need to be some additional configuration added to the
webpack.config.js file in order to leverage the Terser plugin:
https://v4.webpack.js.org/plugins/terser-webpack-plugin/
However, the Caseflow webpack.config.js does not include the Terser configuration at this time,
and so, in keeping parity with Caseflow, we will omit this configuration in eFolder as well
and leave it as a future exercise should it be necessary to enact JS compression.
- ⏪️ Restore overrides for
config.action_dispatch.use_authenticated_cookie_encryptionandconfig.action_dispatch.use_cookies_with_metadata
While testing in PreProd, we discovered that, without these cookie config overrides,
re-authentication was broken -- after logging out, a user could not log back in.
Since the default settings are still optional going forward, we can restore these
overrides and devise a solution to migrate cookies later.
For more details, see Jira story APPEALS-54897:
https://jira.devops.va.gov/browse/APPEALS-54897
-
PG updated to 1.5.7
-
PG regressed from 1.5.7 to 1.1.4 for seperate branches
Co-authored-by: Alec Kagebein [email protected]