sentry-resque 5.9.0 → 5.10.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 66f35be9ab16e76812461332e20a17376606b329360ba5656d66e908e8564f3c
4
- data.tar.gz: de94825fc0fecdcbbaad779321e1bbafa434c6d4bc1b6aa77949d2260e910626
3
+ metadata.gz: 9330bf4a6c1b58fd0ea9eda3b7aa2deb11f1cc24ee5389b8759fb81e60f68ba1
4
+ data.tar.gz: 9a4b528185e21c3ce366d5299a6f2662eebfefccb7f3351c102becdfd420f058
5
5
  SHA512:
6
- metadata.gz: 178fd959e90a2c75fbcb10c6dee653d34975699bd56745b7787be547faf4420460abcc455ca783fd4e1ff6f095d90cb6549f5083d90f13e8e966b5d69f0669b6
7
- data.tar.gz: db4adbcfcddbfc34d7471c084baa48136ed1b487accf81070885e821508d10a90e18360ccf3bbf81e7866adad343703dbd3e107b5efcb96bc34026ee9a8bd472
6
+ metadata.gz: b1e042e071a55537f0f82622a3ee7821329e77188bef1f74f002465e6ce0388fe8fd59d02ed15906fe94803873c23ba75888e482231a25f561b10e997f6f17cb
7
+ data.tar.gz: 8fbe588830b48e63ab2cf8e45dbb03412f36bb13141703b0c4c1b921382264ecbf18e939cd69f719a02ffb0c9de2c5c3c785bf5302fa0fc93cdef22cf59ce596
data/Gemfile CHANGED
@@ -3,6 +3,10 @@ git_source(:github) { |name| "https://github.com/#{name}.git" }
3
3
 
4
4
  # Specify your gem's dependencies in sentry-ruby.gemspec
5
5
  gemspec
6
+ gem "sentry-ruby", path: "../sentry-ruby"
7
+ gem "sentry-rails", path: "../sentry-rails"
8
+
9
+ gem "rails"
6
10
 
7
11
  gem "rake", "~> 12.0"
8
12
  gem "rspec", "~> 3.0"
@@ -10,10 +14,9 @@ gem 'simplecov'
10
14
  gem "simplecov-cobertura", "~> 1.4"
11
15
  gem "rexml"
12
16
 
13
- gem "rails", "< 7.0"
14
-
15
- gem "sentry-ruby", path: "../sentry-ruby"
16
- gem "sentry-rails", path: "../sentry-rails"
17
+ if RUBY_VERSION.to_f >= 2.6
18
+ gem "debug", github: "ruby/debug", platform: :ruby
19
+ gem "irb"
20
+ end
17
21
 
18
22
  gem "pry"
19
- gem "debug", github: "ruby/debug", platform: :ruby if RUBY_VERSION.to_f >= 2.6
@@ -1,5 +1,5 @@
1
1
  module Sentry
2
2
  module Resque
3
- VERSION = "5.9.0"
3
+ VERSION = "5.10.0"
4
4
  end
5
5
  end
@@ -22,6 +22,6 @@ Gem::Specification.new do |spec|
22
22
  spec.executables = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
23
23
  spec.require_paths = ["lib"]
24
24
 
25
- spec.add_dependency "sentry-ruby", "~> 5.9.0"
25
+ spec.add_dependency "sentry-ruby", "~> 5.10.0"
26
26
  spec.add_dependency "resque", ">= 1.24"
27
27
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: sentry-resque
3
3
  version: !ruby/object:Gem::Version
4
- version: 5.9.0
4
+ version: 5.10.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Sentry Team
8
8
  autorequire:
9
9
  bindir: exe
10
10
  cert_chain: []
11
- date: 2023-04-19 00:00:00.000000000 Z
11
+ date: 2023-07-04 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: sentry-ruby
@@ -16,14 +16,14 @@ dependencies:
16
16
  requirements:
17
17
  - - "~>"
18
18
  - !ruby/object:Gem::Version
19
- version: 5.9.0
19
+ version: 5.10.0
20
20
  type: :runtime
21
21
  prerelease: false
22
22
  version_requirements: !ruby/object:Gem::Requirement
23
23
  requirements:
24
24
  - - "~>"
25
25
  - !ruby/object:Gem::Version
26
- version: 5.9.0
26
+ version: 5.10.0
27
27
  - !ruby/object:Gem::Dependency
28
28
  name: resque
29
29
  requirement: !ruby/object:Gem::Requirement
@@ -48,7 +48,6 @@ extra_rdoc_files:
48
48
  files:
49
49
  - ".gitignore"
50
50
  - ".rspec"
51
- - CODE_OF_CONDUCT.md
52
51
  - Gemfile
53
52
  - LICENSE.txt
54
53
  - Makefile
data/CODE_OF_CONDUCT.md DELETED
@@ -1,74 +0,0 @@
1
- # Contributor Covenant Code of Conduct
2
-
3
- ## Our Pledge
4
-
5
- In the interest of fostering an open and welcoming environment, we as
6
- contributors and maintainers pledge to making participation in our project and
7
- our community a harassment-free experience for everyone, regardless of age, body
8
- size, disability, ethnicity, gender identity and expression, level of experience,
9
- nationality, personal appearance, race, religion, or sexual identity and
10
- orientation.
11
-
12
- ## Our Standards
13
-
14
- Examples of behavior that contributes to creating a positive environment
15
- include:
16
-
17
- * Using welcoming and inclusive language
18
- * Being respectful of differing viewpoints and experiences
19
- * Gracefully accepting constructive criticism
20
- * Focusing on what is best for the community
21
- * Showing empathy towards other community members
22
-
23
- Examples of unacceptable behavior by participants include:
24
-
25
- * The use of sexualized language or imagery and unwelcome sexual attention or
26
- advances
27
- * Trolling, insulting/derogatory comments, and personal or political attacks
28
- * Public or private harassment
29
- * Publishing others' private information, such as a physical or electronic
30
- address, without explicit permission
31
- * Other conduct which could reasonably be considered inappropriate in a
32
- professional setting
33
-
34
- ## Our Responsibilities
35
-
36
- Project maintainers are responsible for clarifying the standards of acceptable
37
- behavior and are expected to take appropriate and fair corrective action in
38
- response to any instances of unacceptable behavior.
39
-
40
- Project maintainers have the right and responsibility to remove, edit, or
41
- reject comments, commits, code, wiki edits, issues, and other contributions
42
- that are not aligned to this Code of Conduct, or to ban temporarily or
43
- permanently any contributor for other behaviors that they deem inappropriate,
44
- threatening, offensive, or harmful.
45
-
46
- ## Scope
47
-
48
- This Code of Conduct applies both within project spaces and in public spaces
49
- when an individual is representing the project or its community. Examples of
50
- representing a project or community include using an official project e-mail
51
- address, posting via an official social media account, or acting as an appointed
52
- representative at an online or offline event. Representation of a project may be
53
- further defined and clarified by project maintainers.
54
-
55
- ## Enforcement
56
-
57
- Instances of abusive, harassing, or otherwise unacceptable behavior may be
58
- reported by contacting the project team at stan001212@gmail.com. All
59
- complaints will be reviewed and investigated and will result in a response that
60
- is deemed necessary and appropriate to the circumstances. The project team is
61
- obligated to maintain confidentiality with regard to the reporter of an incident.
62
- Further details of specific enforcement policies may be posted separately.
63
-
64
- Project maintainers who do not follow or enforce the Code of Conduct in good
65
- faith may face temporary or permanent repercussions as determined by other
66
- members of the project's leadership.
67
-
68
- ## Attribution
69
-
70
- This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71
- available at [https://contributor-covenant.org/version/1/4][version]
72
-
73
- [homepage]: https://contributor-covenant.org
74
- [version]: https://contributor-covenant.org/version/1/4/